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 325237 - Crash when hold down space bar
Crash when hold down space bar
Status: RESOLVED DUPLICATE of bug 340827
Product: eog
Classification: Core
Component: collection
2.13.x
Other other
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
: 330340 334614 342118 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-12-29 16:22 UTC by tomkerator
Modified: 2006-07-13 18:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description tomkerator 2005-12-29 16:22:42 UTC
From: TSr <tomkerator@interia.pl>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.12.1
Subject: Crash when hold down space bar

Distribution: Ubuntu 5.10 (breezy)
Package: EOG
Severity: major
Version: GNOME2.12.1 2.13.x
Gnome-Distributor: Ubuntu
Synopsis: Crash when hold down space bar
Bugzilla-Product: EOG
Bugzilla-Component: collection
Bugzilla-Version: 2.13.x
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
When I hold down space button and keep it for few (or more) seconds then
application crash

Steps to reproduce the crash:
1. Go to some directory with small pictures (if there are big fotos then
app doesn't crash)
2. Push down a space bar and wait some time

How often does this happen?
Only for directories with small pictures



Debugging Information:

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

(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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1224808768 (LWP 7313)]
[New Thread -1236722768 (LWP 7316)]
[New Thread -1227002960 (LWP 7314)]
(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 1 (Thread -1224808768 (LWP 7313))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 eog_window_close
  • #11 eog_window_close
  • #12 eog_job_call_finished
  • #13 eog_image_list_iter_equal
  • #14 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 main
  • #0 __kernel_vsyscall





-----------------------------------------------------------------------
ING Nationale-Nederlanden Polska OFE zarabia najwiecej dla swoich
Klientow. Dolacz do prawie 2,2 mln tych, ktorzy dobrze wybrali...
Przystap on-line: >>> http://link.interia.pl/f18eb <<<




------- Bug created by bug-buddy at 2005-12-29 16:22 -------

Comment 1 Lucas Rocha 2006-01-07 04:17:28 UTC
Thanks for the report. I can't reproduce it with EOG 2.13.3. I opened /usr/share/pixmaps which have a baunch of small icons and no crash took place. Could you please add the EOG output for this crash?

Also, 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.
Comment 2 tomkerator 2006-01-07 16:32:47 UTC
If I used images from /usr/share/pixmaps I can't reproduce it too. But try these images: http://fenix.katowice.pl/~tsr/gfx.tar.gz
Comment 3 Lucas Rocha 2006-01-09 01:11:30 UTC
Ok, now I can reproduce it. Confirming.
Comment 4 Lucas Rocha 2006-02-13 02:16:08 UTC
*** Bug 330340 has been marked as a duplicate of this bug. ***
Comment 5 Sergej Kotliar 2006-03-15 10:37:03 UTC
*** Bug 334614 has been marked as a duplicate of this bug. ***
Comment 6 Heikki Henriksen 2006-04-04 10:52:06 UTC
I looked quickly into this, but had to move my priorities before reaching a solution.

Roughly said, there are to many g_asserts around, depending on images not being already loaded. When quickly scrolling back and forwards, one will eventually reach that case (try to load an image that is already loaded), the g_asserts fails and eog crashes.

Of the top of my head at least eog_image_real_load and display_image_data has one of those, which have been around since forever.
Comment 7 Fabio Bonelli 2006-05-17 14:01:20 UTC
*** Bug 342118 has been marked as a duplicate of this bug. ***
Comment 8 Lucas Rocha 2006-07-13 18:00:51 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 340827 ***