Mailinglist Archive: opensuse-bugs (14446 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=434561

User eich@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=434561#c31


Egbert Eich <eich@xxxxxxxxxx> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
             Status|NEW                                             |RESOLVED
         Resolution|                                                |INVALID




--- Comment #31 from Egbert Eich <eich@xxxxxxxxxx>  2008-10-21 04:56:16 MDT ---
(In reply to comment #30 from Maciej Pilichowski)
> Nobody didn't answer if next step in installer is something with the network.
> The answer is -- yes.
>
> Now, some new info.
>
> > How much memory does the system in the VirtualBox have? 
>
> 256MB. It was sufficient for all other Linux distros.

You are running from a livecd, aren't you? Those livecds typically use a lot of
memory as they need to keep parts of the non-permanent file system data in RAM.

> > Could it be that the Xserver  got killed due to an out-of-memory condition?
>
> Yes, I increased RAM to 1GB and installer get to next step. This way I get to
> know, there is network-related step.

Just there or did the install succeed?

> Some remarks:
> a) crashing an app just because there is no memory is not very user-friendly
> b) installer should fit in this RAM, but if it is not now, _it_ should crash,
> not X

For 11.1 256MB is very low - if you don't have swap space in addition.
At the moment I don't know who kills X and how it dies. In any case it seems to
be termniated normally (SIGTERM) not with (SIGSEGV or SIGKILL).
The instance which terminates processes in a low memory situation usually does
not know about X. The discussion about the best policy to apply in such a
situation are as old as the computer.
It takes place elsewhere. There are very few complaints about this issue,
though,  most use cases this seems to be pretty irrelevant.
> So maybe now you are curious what is about that network I keep mentioning.
> Well, I set RAM back to 256MB, I turned network off, and suddenly it was 
> enough
> RAM to go to 2nd step in installer. No X restarting.

OK. So possibly the yast networking module caused your memory to go low. This
doesn't answer why your memory went low under normal usage. You can use tools
like free, ps, top etc. to monitor memory consumption while you are working and
try to identify who needs how much memory.

> > have you tried the LiveCD on a physical system (not inside a Vbox)?
>
> Nope. Currently my intention is to use opensuse inside VB. Not only for betas,
> but for 11.1 too.

I asked this question merely to have more information for tracking down this
issue. In cases where we cannot easily reproduce a problem locally we need to
ask the user to try different things in his environment.

To me this is not really a bug. At least not one in X.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.