GNOME Bugzilla – Bug 481729
Crash browsing thru images when one is empty-Bug Reporting Tool crash too.
Last modified: 2009-09-18 12:37:08 UTC
Reproducible error: I have simply two jpg images files in my directory: a normal one (call it 'good.jpg') and an empty one (call it 'empty.jpg'). I used gthumb to open the empty one (didn't realize at that time it was empty ;-). The application starts and trying to browse ahead with the arrow button causes the crash. FYI: If I repeat the same procedure by opening the good.jpg, and browsing everything is fine. I reproduced this error many times easily. Consequently, the Bug Reporting Tool starts but when I press the 'send' button the following message appears (partially in greek language): -------------------------------------------------------------------------------- Ο Βοηθός σφαλμάτων αντιμετώπισε ένα σφάλμα κατά την υποβολή της αναφορά σας στον Bugzilla server. Οι λεπτομέρειες του σφάλματος αναφέρονται παρακάτω. Αποτυχία ανάλυσης της xml-rpc response. Η απάντηση: Αδυναμία ανάλυσης απάντησης XML-RPC 3 <?xml version="1.0" encoding="UTF-8"?> <methodResponse><fault><value><struct><member><name>faultString</ name><value><string>Application failed during request deserialization: not well-formed (invalid token) at line 23, column 0, byte 1521 at /usr/lib64/ perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/Parser.pm line 187 </string></value></member><member><name>faultCode</ name><value><string>Client</string></value></member></struct></ value></fault></methodResponse> ------------------------------------------------------------------------------- I really don't know whether the two types of crash are related. I reported this bug only here (as the first one involved gthumb). Trying to avoid any confusion with bug report duplication I don't make other report. Thank you very much for your attention and help. Hope it's been helpful Regards Dimitri
I can't reproduce this. What version are you using? 2.10.6? - Mike
(In reply to comment #1) > I can't reproduce this. What version are you using? 2.10.6? > > - Mike > I just checked that it is still reproduced equally for me as described before. The GNOME gthumb version used is 2.10.5. Dimitris
Can you upgrade to 2.10.6 and try again? A lot of bugs were fixed in 2.10.6. If it still occurs with 2.10.6, please generate a backtrace (http://live.gnome.org/GettingTraces) and attach it to this bug report. - Mike
(In reply to comment #3) > Can you upgrade to 2.10.6 and try again? A lot of bugs were fixed in 2.10.6. > > If it still occurs with 2.10.6, please generate a backtrace > (http://live.gnome.org/GettingTraces) and attach it to this bug report. > > - Mike > I have upgraded to 2.10.6 and I still observe this effect. I admit that I didn't explain one detail for which I am facing also a difficulty to attach the backtrace: to produce the crash I need to open the empty file by the command line as: gthumb empty.jpg (the empty file) With gdb I cannot (it might be some way but I don't know how) pass an argument indicating the effect of 'press arrow button'. Trying to do something similar, gdb expects (logically) a core file. In case I am trying with just invoking 'gthumb' and then selecting an image and go into browsing using the arrow-button nothing bad happens. I just remind also that if I first invoke gthumb with a non-empty file everything is also ok. I just wanted to include some diagnostic message from the shell-window that I hadn't observed so far: [oreibaths@localhost ~]$ gthumb empty.jpg (gthumb:30618): libgnomevfs-CRITICAL **: gnome_vfs_mime_application_launch_with_env: assertion `uris != NULL' failed (gthumb:30618): libgnomevfs-CRITICAL **: gnome_vfs_mime_application_launch_with_env: assertion `uris != NULL' failed (gthumb:30618): libgnomevfs-CRITICAL **: gnome_vfs_mime_application_launch_with_env: assertion `uris != NULL' failed (gthumb:30618): Gtk-CRITICAL **: gtk_tree_path_get_indices: assertion `path != NULL' failed Cannot access memory at address 0x0 Cannot access memory at address 0x0 Thanks Dimitris
I just wanted to include the following messages. The first lines are as before, but the last are from the second type of crash involving the bug reporting tool when 'Send' is pressed. [oreibaths@localhost ~]$ gdb `gthumb empty.jpg` (gthumb:30839): libgnomevfs-CRITICAL **: gnome_vfs_mime_application_launch_with_env: assertion `uris != NULL' failed (gthumb:30839): libgnomevfs-CRITICAL **: gnome_vfs_mime_application_launch_with_env: assertion `uris != NULL' failed (gthumb:30839): libgnomevfs-CRITICAL **: gnome_vfs_mime_application_launch_with_env: assertion `uris != NULL' failed (gthumb:30839): Gtk-CRITICAL **: gtk_tree_path_get_indices: assertion `path != NULL' failed Cannot access memory at address 0x0 Cannot access memory at address 0x0 (bug-buddy:30850): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:30850): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:30850): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:30850): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Thanks Dimitris
Hmm, I still don't get a crash, but running: gthumb --g-fatal-warnings empty.jpg gives: Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.22.2-42.fc6 #1 SMP Wed Aug 15 12:34:26 EDT 2007 i686 X Vendor: The XFree86 Project, Inc X Vendor Release: 40300000 Selinux: No Accessibility: Disabled Memory status: size: 96899072 vsize: 0 resident: 96899072 share: 0 rss: 33767424 rss_rlim: 0 CPU usage: start_time: 1191412443 rtime: 0 utime: 74 stime: 0 cutime:66 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gthumb' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208609056 (LWP 25343)] [New Thread -1277178992 (LWP 25354)] [New Thread -1276650608 (LWP 25353)] [New Thread -1276122224 (LWP 25352)] [New Thread -1253082224 (LWP 25348)] [New Thread -1252553840 (LWP 25346)] 0x00110402 in __kernel_vsyscall ()
+ Trace 167378
Thread 1 (Thread -1208609056 (LWP 25343))
Dimitrios, I committed a patch to svn (rev 2007) that fixes the gnome_vfs_mime_application_launch_with_env warnings. I haven't duplicated your gtk_tree_path_get_indices warnings, though, so I'm not sure if your crash is fixed. Do you know how to compile and test from svn? Can you test the new code? - Mike
Mike, I am not quite sure how the code structure is. If you provide just with minimum directions I believe I could do it (extrapolating the rest by myself). -Dimitrios
Dimitrios, These are the basic steps for compiling gthumb from svn: cd ~ svn checkout http://svn.gnome.org/svn/gthumb/gthumb-2-10 cd gthumb-2-10 ./autogen.sh (on Redhat/fedora: ./autogen.sh --prefix=/usr) make su make install exit gthumb Let me know how it goes... - Mike
I downloaded, compiled and ran the updated code, but I observed the same effect. I need to say though that in my 2.10.6 upgrade I had missed the intltool package, which I installed (required by autogen-apologies!) before testing the new code. Maybe, a positive thing is that I managed to obtain the backtrace (from new code testing) which I list below. I am not sure how much newer info are included wrt the previous one listed above. A last thing to say is that trying to run gthumb --g-fatal-warnings empty.jpg causes a direct crash. Thanks (also for your directions about testing) Backtrace (by invoking 'gthumb empty.jpg'+ arrow-button): ------------------------------------------------------- Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 65757184 vsize: 65757184 resident: 27672576 share: 21495808 rss: 27672576 rss_rlim: 4294967295 CPU usage: start_time: 1191537155 rtime: 47 utime: 42 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/local/bin/gthumb' [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209165280 (LWP 28417)] [New Thread -1244120176 (LWP 28424)] [New Thread -1243591792 (LWP 28423)] [New Thread -1243063408 (LWP 28422)] [New Thread -1232045168 (LWP 28420)] [New Thread -1231516784 (LWP 28419)] 0x00110402 in __kernel_vsyscall ()
+ Trace 167826
Thread 1 (Thread -1209165280 (LWP 28417))
----------- .xsession-errors (2498 sec old) --------------------- localuser:oreibaths being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2770 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running seahorse nautilus module initialized error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: livna. Please verify its path and try again ** Message: <info> Έχετε συνδεθεί στο ασύρματο δίκτυο 'Japonida'. kbuildsycoca running... (gnome-terminal:3109): Vte-WARNING **: Δεν υπάρχει χειριστής για τη σειρά ελέγχου `device-control-string' ορίσθηκε. --------------------------------------------------
Hmm... gth_browser_show_next_image is executing, even though browser=0x0. Which doesn't seem right... - Mike
I have a recurring crash that might be related. While copying photos from a 4GB memory stick I'm often tempted to start browsing them in gthumb, eventhough the files are still copying. The trouble is that gthumb tends to crash trying to preview and/or view the partial file(s) that havn't finished copying (yet). So I wonder if gthumb needs to be a bit gentler about incomplete files and tracking when files change, and retrying after some reasonable period of time. - Nigel
Marking as obsolete, due to work in ext branch (the new development version). http://live.gnome.org/gthumb