GNOME Bugzilla – Bug 499173
crash in Open Folder: opening a folder with 30...
Last modified: 2007-12-17 12:21:06 UTC
Version: 2.20.0 What were you doing when the application crashed? opening a folder with 3000 images for the second time Distribution: Debian lenny/sid Gnome Release: 2.20.1 2007-10-26 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome Memory status: size: 195538944 vsize: 195538944 resident: 146432000 share: 14274560 rss: 146432000 rss_rlim: 4294967295 CPU usage: start_time: 1195824011 rtime: 2321 utime: 1997 stime: 324 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c6d9f0 (LWP 18718)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 179361
Thread 1 (Thread 0xb6c6d9f0 (LWP 18718))
----------- .xsession-errors (8800 sec old) --------------------- (nautilus:3212): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:3212): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:3212): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:3212): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:3212): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:3212): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:3212): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ...Too much output, ignoring rest... --------------------------------------------------
Created attachment 99528 [details] sample image 1. create a new folder and place 3000 copies of the image on it. 2. open the folder with Nautilus and wait for all the thumbnails to be generated 3. close the folder window and open it again 4. After a while Nautilus crashes
thanks for reporting! unique (nautilus:3212): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
I tried with Gnome 2.21 and 1,000 copies of that image but I cannot make nautilus crash Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
1000 is not enough, but you don't really have to create 3000 copies of the image, just use hard links to replicate it! BTW, I first encounter this bug in a folder with around 800 real different images, so it is not an artificial bug, it can happen under normal conditions. Cheers
Distribution: Debian lenny/sid Gnome Release: 2.20.1 2007-10-26 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome Memory status: size: 202354688 vsize: 202354688 resident: 153616384 share: 14266368 rss: 153616384 rss_rlim: 4294967295 CPU usage: start_time: 1195865713 rtime: 2580 utime: 2314 stime: 266 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6c8c9f0 (LWP 27423)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 179420
Thread 1 (Thread 0xb6c8c9f0 (LWP 27423))
----------- .xsession-errors (14 sec old) --------------------- I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : Too many open files I/O error : ...Too much output, ignoring rest... --------------------------------------------------
This problem has been fixed already in our software repository. Please ask Debian to provide updated packages. *** This bug has been marked as a duplicate of 483884 ***