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 667964 - Nautilus crashes (and blocks the entire system) when the user tries to view a gif file's properties.
Nautilus crashes (and blocks the entire system) when the user tries to view a...
Status: RESOLVED NOTGNOME
Product: nautilus
Classification: Core
Component: File Properties Dialog
3.2.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-01-15 18:26 UTC by Andreu Correa Casablanca
Modified: 2012-01-18 15:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
One of the images that makes nautilus crash (1.91 KB, image/gif)
2012-01-15 18:26 UTC, Andreu Correa Casablanca
Details
Another image that crashes nautilus when I try to view its properties (1.15 KB, image/gif)
2012-01-18 14:02 UTC, Andreu Correa Casablanca
Details
Memory consumption graph. (716.83 KB, image/png)
2012-01-18 14:39 UTC, Andreu Correa Casablanca
Details
The backtrace (29.04 KB, text/plain)
2012-01-18 15:18 UTC, Andreu Correa Casablanca
Details

Description Andreu Correa Casablanca 2012-01-15 18:26:10 UTC
Created attachment 205304 [details]
One of the images that makes nautilus crash

Nautilus crashes (and blocks the entire system) when the user tries to view a gif file's properties.

Nautilus Version: 3.2.1
Ubuntu Version: 11.10 64 bits

I atach the files that makes nautilus crash
Comment 1 André Klapper 2012-01-15 21:09:38 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so and make sure to install debug packages first. Thanks in advance!
Comment 2 Rui Matos 2012-01-15 21:20:00 UTC
(In reply to comment #0)
> Nautilus crashes (and blocks the entire system) when the user tries to view a
> gif file's properties.

You mean right-click > Properties, right? I can't reproduce a crash here with nautilus from master.
Comment 3 Andreu Correa Casablanca 2012-01-15 21:53:33 UTC
(In reply to comment #2)
> (In reply to comment #0)
> > Nautilus crashes (and blocks the entire system) when the user tries to view a
> > gif file's properties.
> 
> You mean right-click > Properties, right? I can't reproduce a crash here with
> nautilus from master.

Yes, I mean right-click > Properties .

I can't obtain the stack trace yet, but I've observed a little issue that may be is related.

The bug happens in my laptop, with an integrated Intel graphics card, but not in my "big" PC (with an ATI graphics card). In any case, in my big PC the right-click properties menu is much more slower when I try with GIF files than when I try with PNG files.

It's possible that my laptop (with an "older" CPU [Centrino Core 2 Duo]) can't assume a big cpu load related with the GIF file?

Tomorrow I'll post here the stacktrace, good night :) .
Comment 4 Andreu Correa Casablanca 2012-01-18 14:02:54 UTC
Created attachment 205525 [details]
Another image that crashes nautilus when I try to view its properties
Comment 5 André Klapper 2012-01-18 14:07:45 UTC
As I said before I cannot reproduce it, and a stacktrace is needed.
Comment 6 Andreu Correa Casablanca 2012-01-18 14:39:15 UTC
Created attachment 205528 [details]
Memory consumption graph.

I've discovered that nautilus blocks my laptop because when I try to view the gif file properties the memory consumption grows fast as light (to consume more than 3GB :s ).

The graf of memory consumption is attached, you can see the peak that appears when i try to see the file properties.

At the moment, I couldn't print the stacktrace :( , I'm not experienced with gdb. I'll try with valgrind.

Final comment: I saw that there are many bugs related with nautilus, gif files and memory consumption. Maybe these bugs are related.
Comment 7 André Klapper 2012-01-18 14:41:01 UTC
(In reply to comment #6)
> I'm not experienced with gdb.

https://live.gnome.org/GettingTraces/Details#gdb-already-running
Comment 8 Andreu Correa Casablanca 2012-01-18 15:18:48 UTC
Created attachment 205532 [details]
The backtrace

Here is the backtrace :)
Comment 9 André Klapper 2012-01-18 15:28:28 UTC
Thanks! Pasting the backtrace here so traceparser can take a look at it:

Program received signal SIGINT, Interrupt.
__memset_sse2 () at ../sysdeps/x86_64/multiarch/../memset.S:916
916	../sysdeps/x86_64/multiarch/../memset.S: No existe el archivo o el directorio.
	in ../sysdeps/x86_64/multiarch/../memset.S
(gdb) backtrace full
  • #0 __memset_sse2
    at ../sysdeps/x86_64/multiarch/../memset.S line 916
  • #1 std::string::_M_replace_aux(unsigned long, unsigned long, unsigned long, char)
    from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  • #2 GIF_MetaHandler::CacheFileData()
    from /usr/lib/libexempi.so.3
  • #3 XMPFiles::OpenFile(char const*, unsigned int, unsigned int)
    from /usr/lib/libexempi.so.3
  • #4 WXMPFiles_OpenFile_1
    from /usr/lib/libexempi.so.3
  • #5 TXMPFiles<std::string>::OpenFile(char const*, unsigned int, unsigned int)
    from /usr/lib/libexempi.so.3
  • #6 TXMPFiles<std::string>::TXMPFiles(char const*, unsigned int, unsigned int)
    from /usr/lib/libexempi.so.3
  • #7 xmp_files_open_new
    from /usr/lib/libexempi.so.3
  • #8 load_location
    at nautilus-image-properties-page.c line 571
  • #9 get_property_pages
    at nautilus-image-properties-page.c line 663
  • #10 get_property_pages
    at nautilus-image-properties-page.c line 626
  • #11 append_extension_pages
    at nautilus-properties-window.c line 4628
  • #12 create_properties_window
    at nautilus-properties-window.c line 4931
  • #13 is_directory_ready_callback
    at nautilus-properties-window.c line 5069
  • #14 is_directory_ready_callback
    at nautilus-properties-window.c line 5057
  • #15 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1861
  • #16 g_main_context_dispatch
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #17 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-3.so.0
  • #20 g_application_run
    from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #21 main
    at nautilus-main.c line 102

Comment 10 Rui Matos 2012-01-18 15:37:42 UTC
SIGINT? Did you Ctrl+C ?

The trace seems to point at libexempi and not nautilus though.
Comment 11 Andreu Correa Casablanca 2012-01-18 15:49:10 UTC
yes, I did Ctrl+C (the system becomes blocked if i don't do it).

I have to post here the stacktrace with the libxempi-dbg installed... or the bug must be traslated the libxempi team?
Comment 12 André Klapper 2012-01-18 15:54:14 UTC
The crash is in libexempi, hence closing as NOTGNOME.

Fedora 16 ships        exempi 2.1.1-2.fc15.i686
Ubuntu 11.10 ships libexempi3 2.1.1-1build2

As written I cannot reproduce the problem in Fedora 16. 
=> Please file a bug report in the bugtracker of your distribution at https://launchpad.net/ubuntu .
Upstream reports could be filed at https://bugs.freedesktop.org/enter_bug.cgi?product=exempi however as it works on Fedora 16 I don't think that it makes sense at this stage.