nautilus crashed with SIGSEGV in magazine_cache_push_magazine()

[Daniel Hahler]

Binary package hint: nautilus

No info available.

ProblemType: Crash
Architecture: i386
Date: Tue Nov 6 13:44:27 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.20.0-0ubuntu7
PackageArchitecture: i386
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcCwd: /home/daniel
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/daniel/bin:/home/daniel/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 magazine_cache_push_magazine (ix=1,
 thread_memory_magazine2_unload (tmem=<value optimized out>,
 IA__g_slice_free_chain_with_offset (mem_size=12,
 IA__g_list_free (list=0x81aa880)
 eel_enumeration_free () from /usr/lib/libeel-2.so.2
Title: nautilus crashed with SIGSEGV in magazine_cache_push_magazine()
Uname: Linux base 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev scanner src vboxusers video

[Apport retracing service (apport)]

StacktraceTop:magazine_cache_push_magazine (ix=1, magazine_chunks=<value optimized out>,
thread_memory_magazine2_unload (tmem=<value optimized out>, ix=352157891)
IA__g_slice_free_chain_with_offset (mem_size=12, mem_chain=0x81aa880,
IA__g_list_free (list=0x81aa880) at /build/buildd/glib2.0-2.14.1/glib/glist.c:53
eel_enumeration_free (enumeration=0x81ab090) at eel-enumeration.c:90

[Pedro Villavicencio (pedro)]

Thanks for your report, may you tell us a few steps for trigger the crash?

[Daniel Hahler (blueyed)]

No, unfortunately I cannot reproduce it. It might be related to bug 150471 IIRC.

From a quick search in Gnome's bug tracker and other nautilus bugs this might be related to creating a lot of new files, e.g. when checking out some source code repository, using pbuilder etc.

I'm not using nautilus regularly, mainly when testing some Ubuntu (vs. Kubuntu) related bugs/things.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

[Blake Escritt (bescritt)]

My report, Bug 203339, was marked a duplicate of this one and I am willing to send any logs or information you might need.
I haven't been able to trigger the bug at will either. it seems intermittent. If it starts happening again I'll pay close attention to what I'm doing. It first started happening after several failed attempts at getting Firefox 2.0.0.12 to download package updates. Then it proceeded to happen, even after warm and cold boots, independently of Firefox. My guess, from the variable severity of the crashes, is it's a form of memory-corruption error. Since the symptoms persisted thru several reboots, it might be a hardware problem or a corrupted cache somewhere. I'll run memtest86+ the next time I boot the machine, and I'll come back with its results ASAP.

[Blake Escritt (bescritt)]

My system memory is fine, according to memtest86+. Additionally, I ran a full fsck on all of my partitions, with no errors detected. Any suggestions on what else I might do to pinpoint the error(, besides wait for it to start occurring again)?

[Sebastien Bacher (seb128)]

could you try if that's still an issue using hardy?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.