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 307248 - Crash when browsing folder of svg images
Crash when browsing folder of svg images
Status: RESOLVED DUPLICATE of bug 154346
Product: nautilus
Classification: Core
Component: general
2.10.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-11 07:58 UTC by apater
Modified: 2005-06-21 18:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
A SVG Image (135.98 KB, image/svg+xml)
2005-06-11 23:13 UTC, apater
Details

Description apater 2005-06-11 07:58:42 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: Crash when browsing folder of svg images
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. Open a nautilus window
2. browse to a folder with a lot of svg files
3. scroll down, nautilus crashes

Expected Results:
system quickly renders thumbnails of images, allow one to quickly view
the entire contents of the folder

How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223908096 (LWP 9099)]
[New Thread -1238660176 (LWP 13721)]
[New Thread -1237816400 (LWP 9137)]
[New Thread -1237550160 (LWP 9136)]
[New Thread -1237283920 (LWP 9135)]
[New Thread -1237017680 (LWP 9134)]
[New Thread -1236358224 (LWP 9133)]
[New Thread -1226306640 (LWP 9123)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 8 (Thread -1226306640 (LWP 9123))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-11 07:58 UTC -------


Unknown version 2.10.0 in product nautilus.  Setting version to "2.10.x".

Comment 1 Martin Wehner 2005-06-11 09:57:33 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Can you get us one with debugging symbols?
Please see http://live.gnome.org/GettingTraces for more information on how to do
so. Alternatively, you could try to find the image that crashes and attach it to
this bug.
Comment 2 apater 2005-06-11 23:13:54 UTC
Created attachment 47625 [details]
A SVG Image

nautilus hangs trying to create a thumbnail of this image.
Comment 3 apater 2005-06-11 23:28:25 UTC
Is this what you need as a stack trace?

(gdb) thread apply all bt

Thread 5 (Thread -1226306640 (LWP 10395))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall



The folder contains 189 svg images, and is located at
/usr/share/openclipart/svg/unsorted/ on this system. It was installed from the
http://ftp.ankara.edu.tr/ubuntu/pool/universe/o/openclipart/openclipart-svg_0.13.2+dfsg-1_all.deb
 package.

There is not a specific file which causes the crash, that I can see at least.
nautilus crashes after about 30 seconds of opening the folder, apparently while
trying to create the thumbnails.

Further testing was performed on the
/usr/share/openclipart/svg/signs_and_symbols/ folder which contains 214 svg
images. Nautilus did not crash on this folder, but neither did it finish
renduring the thumbnails. It got about halfway through, but hung on the
kansas_flag_dave_reckonin_01.svg  image. At this point the system was very
unresponsive with the HD thrashing constantly. I was able, however, to go up one
level, back to the /usr/share/openclipart/svg/ folder, and the system eventually
returned to normal.

I copied the kansasflag_dave_reckonin_01.svg file to a different folder.
Nautilus refuses to create a thumbnail for it, the system becomes unresponsive
with the harddrive thrashing constantly. 
Comment 4 Vincent Noel 2005-06-21 18:11:19 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

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