Bug 133530
|
Description
Tim Vismor
2004-09-24 17:21:24 UTC
Created attachment 104276 [details]
System log of the event
Created attachment 104277 [details]
System monitor recording of the event
Can you strace nautilus when this happens. Remove it from the session and kill it, then start it as "strace -o nautilus.log nautilus" and attach nautilus.log here. Created attachment 104437 [details]
strace of nautilus during oom incident
Per your request, I ran the nautilus browser under strace and generated a trace
of an OOM incident. The script of the session was similar to the original bug
report.
Hmm. It doesn't seem to allocate a lot of memory. Maybe one of the threads does it. Can you try "strace -o nautilus.log -tt -f nautilus" instead? Also, could you try this not running as root? Created attachment 104503 [details]
Output from strace -o nautilus3.log -tt -f nautilus --browser
Attached is the output of strace with the additional arguments. This trace was
run as root. The OOM triggering scenario was similar to the previous two
events. FYI, terminal output was as follows:
[root@redbud ~]# strace -o nautilus3.log -tt -f nautilus --browser
PANIC: attached pid 4596 exited
PANIC: handle_group_exit: 4596 leader 4595
[root@redbud ~]#
The output occurred immediately after running strace, before any user
interaction with nautilus.
Will try this as a normal user now.
Created attachment 104504 [details]
strace output from normal user account
This trace is from a user account with normal privileges. For what its worth, I
looked at the system log associated with this OOM event and only nautilus was
killed. Normally, daemons like named and httpd are shut down first.
Terminal output was similar to the previous report:
[tdv@redbud ~]$ strace -o nautilus.log -tt -f nautilus --browser
PANIC: attached pid 5884 exited
PANIC: handle_group_exit: 5884 leader 5848
[tdv@redbud ~]$
Created attachment 104505 [details]
Anomaly in tree view prior to previous OOM
This may be the subject of another bug report or it may be relevant to the
current discussion.
When the nautilus browser started during previous OOM incident, the tree view
in its left pane was "different". In particular, note
(a) The samba share "Dogwood" is located above the local file system in the
tree. It is normally, displayed beneath the "Filesystem".
(b) The "Filesystem" icon does not a symbol for expanding its node in the tree.
I have seen this problem sporadically with various versions of nautilus
thoughout August and September.
Note: The current OS is Rawhide as of 9/28/04.
Created attachment 104506 [details]
Previous screen shot as png.
Sorry, I forgot to mark the tree view screen shot as a png and it was saved as
text.
Its very strange. It doesn't look from the trace like nautilus is allocating a lot of memory. I have no idea why this is happening. Since I updated from Rawhide today (9/29/04), I have not encountered this problem. Looking over today's changes, it struck me that a bug (http://bugzilla.gnome.org/show_bug.cgi?id=153759) which was fixed in gnome-vfs may have been the culprit. Apparently, a bug in the desktop file parser could generate gigabyte memory allocations (by computing string length using inappropriate pointer arithemtic). Since desktop file parsing is now used for mime type determination (which is used for icon selection, etc), it seems to me that encountering some ill-formed (in the sense that it triggered the bug) desktop file could have caused the OOM condition. Just speculation. Yes. That is likely the problem. I'll close this for now then. Reopen if you see it again. |