After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 521446 - crash in Open Folder: scrolling a list of imag...
crash in Open Folder: scrolling a list of imag...
Status: RESOLVED DUPLICATE of bug 483884
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-09 20:45 UTC by scion
Modified: 2008-03-10 11:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description scion 2008-03-09 20:45:11 UTC 
Version: 2.20.0

What were you doing when the application crashed?
scrolling a list of images (thus large files) awaiting the browser to update the thumbnails


Distribution:                 Solaris Express Developer Edition 1/08 snv_79b X86
Gnome Release: 2.20.1 2007-11-19 (Sun Microsystems, Inc.)
BugBuddy Version: 2.20.1

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus

Memory status: size: 160894976 vsize: 160894976 resident: 42008576 share: 393216 rss: 42008576 rss_rlim: 0
CPU usage: start_time: 0 rtime: 2346 utime: 19160687 stime: 4301223 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/bin/nautilus'

(no debugging symbols found)
sol-thread active.
Retry #1:
Retry #2:
Retry #3:
Retry #4:
[New LWP    1        ]
[New Thread 1 (LWP 1)]

+ Trace 191898

Thread 1 (LWP 1)

  • #0 _waitid
    from /lib/libc.so.1
  • #1 _waitpid
    from /lib/libc.so.1
  • #2 waitpid_cancel
    from /lib/libc.so.1
  • #3 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #5 __1cNrun_bug_buddy6Fpkclp0_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 __1cMcheck_if_gdb6Fpv_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 _ex_text0
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 sigfatal_handler
  • #9 __sighndlr
    from /lib/libc.so.1
  • #10 call_user_handler
    from /lib/libc.so.1
  • #11 <signal handler called>
  • #12 nautilus_icon_factory_possibly_free_cached_icon
  • #13 g_hash_table_foreach_remove_or_steal
    from /usr/lib/libglib-2.0.so.0
  • #14 g_hash_table_foreach_remove
    from /usr/lib/libglib-2.0.so.0
  • #15 nautilus_icon_factory_sweep
  • #16 g_timeout_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 main 

Thread 4 (Thread 29 (LWP 29)):
#-1 0xf9b11355 in jpeg_fill_bit_buffer () from /usr/lib/libjpeg.so.62
No symbol table info available.

Thread 3 (LWP    29        ):
#-1 0xf9b11355 in jpeg_fill_bit_buffer () from /usr/lib/libjpeg.so.62
No symbol table info available.

Thread 2 (Thread 1 (LWP 1)):
#-1 0xfeee34c7 in _waitid () from /lib/libc.so.1
No symbol table info available.

Thread 1 (LWP    1        ):
#-1 0xfeee34c7 in _waitid () from /lib/libc.so.1
No symbol table info available.
#-1 0xfeee34c7 in _waitid () from /lib/libc.so.1


----------- .xsession-errors (154715 sec old) ---------------------
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/dt/config/Xsession.jds
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-10 11:03:12 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 483884 ***