GNOME Bugzilla – Bug 350452
NULL key hash table lookup
Last modified: 2007-05-17 20:52:47 UTC
What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.91 2006-08-08 (Ubuntu) BugBuddy Version: 2.15.90 Memory status: size: 239194112 vsize: 239194112 resident: 49123328 share: 25821184 rss: 49123328 rss_rlim: -1 CPU usage: start_time: 1155050486 rtime: 26918 utime: 4529 stime: 22389 cutime:65 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47129242367728 (LWP 9779)] 0x00002add1df86dbf in waitpid () from /lib/libpthread.so.0
+ Trace 70096
Thread 1 (Thread 47129242367728 (LWP 9779))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report? *** This bug has been marked as a duplicate of 335114 ***
sorry mislead by our simple-dup-finder
CCing Benoit can you guys please install glib and nautilus debugging packages? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
*** Bug 354188 has been marked as a duplicate of this bug. ***
*** Bug 354516 has been marked as a duplicate of this bug. ***
Ubuntu bug about that: https://launchpad.net/products/nautilus/+bug/60078
*** Bug 356567 has been marked as a duplicate of this bug. ***
Debug backtrace from the Ubuntu bug: "Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 79785984 vsize: 0 resident: 79785984 share: 0 rss: 35590144 rss_rlim: 0 CPU usage: start_time: 1158585338 rtime: 0 utime: 1476 stime: 0 cutime:1386 cstime: 0 timeout: 90 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226684752 (LWP 5011)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72719
stef, there must be something spectial in that folder that makes nautilus crash. Can you narrow it down?
*** Bug 357753 has been marked as a duplicate of this bug. ***
Christian, any reason you set that back as NEEDINFO back? It has a debug backtrace
yap I asked if the reporter can track it down to the item causing the crash. hmm on the other hand we have a couple of duplicates and valueable traces so I am confirming this report now.
Maybe nautilus_file_get_uri returns NULL. Possibly, file->details->directory->details->uri is NULL. It would be very helpful to get a list of affected GnomeVFS modules. On the other hand, nautilus_directory_new asserts that precisely this variable may not be NULL.
same stacktrace as bug 343488, copying christian's comment
*** Bug 359948 has been marked as a duplicate of this bug. ***
Hmm, short of the NULL pointer parameter (directory vs changed_files) in the nautilus_directory_emit_change_signals() call, this looks like the very same issue as bug 343488. Also, bug 350975 comment 56 got an identical stacktrace as bug 343488. Although that one differs from the original and the duplicates (without debugging symbols). Could a Nautilus developer please have a close look at these? Are they actually the same issue? Note that bug 350975 is a blocker.
*** Bug 361861 has been marked as a duplicate of this bug. ***
*** Bug 362086 has been marked as a duplicate of this bug. ***
*** Bug 362431 has been marked as a duplicate of this bug. ***
*** Bug 362581 has been marked as a duplicate of this bug. ***
Yes, this very much looks like a dup of 343488. *** This bug has been marked as a duplicate of 343488 ***
*** Bug 362887 has been marked as a duplicate of this bug. ***
Yay, turns out my assumtions in comment 16 where dead right. :) Alexander, I also just spotted a trail of evidence. The reporter of bug 361537 (which is a duplicate of this one) managed to reproduce and gather a stacktrace with debugging symbols, filed as bug 362581 -- marked instantly as a duplicate of bug 350452, which is a duplicate of bug 343488. *phew* Thus, this bug indeed is the same issue as bug 343488. Doesn't only look like a dupe. ;)
If anybody of the reporters do not use pre-compiled packages (provided by their distributor), but compile from the source code, please help us by applying the patch at http://bugzilla.gnome.org/show_bug.cgi?id=343488#c25 in order to test if this fixes this crash. Feedback highly welcome and appreciated (please add any comments to bug 343488), thanks everybody in advance!
*** Bug 384760 has been marked as a duplicate of this bug. ***
*** Bug 392580 has been marked as a duplicate of this bug. ***
*** Bug 394668 has been marked as a duplicate of this bug. ***
*** Bug 395386 has been marked as a duplicate of this bug. ***
*** Bug 396397 has been marked as a duplicate of this bug. ***
*** Bug 426568 has been marked as a duplicate of this bug. ***
*** Bug 439101 has been marked as a duplicate of this bug. ***