Bug 330506 – eog dies because of not enough RAM

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 330506 - eog dies because of not enough RAM


Summary:	eog dies because of not enough RAM


Status:	RESOLVED DUPLICATE of bug 315147

Product:	eog
Classification:	Core
Component:	general
Version:	2.8.2
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	EOG Maintainers
QA Contact:	EOG Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-02-09 09:55 UTC by reuleaux
Modified:	2006-02-09 21:14 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description reuleaux 2006-02-09 09:55:55 UTC

Distribution: Debian 3.1
Package: EOG
Severity: normal
Version:  2.8.2
Synopsis: eog dies because of not enough RAM
Bugzilla-Product: EOG
Bugzilla-Component: general
Bugzilla-Version: 2.8.2
BugBuddy-GnomeVersion: 2.0 (2.8.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. step to a directory with many .jpg files (280 files in my case, 40M altogether)
2. open eog with that directory as an argument: eog . &
3. now with the right arrow step from picture to picture
    somewhere behind the middle (ca. 140-200 pics) eog dies
    with an error message: not enough RAM (I have 512M)

Expected Results:
  at least eog should not die,
  maybe the OS (Debian GNU/Linux, sarge in my case) should swap
  maybe some warning upfront


How often does this happen?
  reproducibly every time I open eog with that directory

Additional Information:
  



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1087908352 (LWP 27443)]
(no debugging symbols found)
0x407d9561 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 66033

Thread 1 (Thread 1087908352 (LWP 27443))

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/tls/libc.so.6
#4 abort
from /lib/tls/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 ??
from /usr/lib/libgthread-2.0.so.0
#8 ??
from /usr/lib/libgthread-2.0.so.0
#9 ??
#10 ??
from /usr/lib/libgthread-2.0.so.0
#11 ??
from /usr/lib/libgthread-2.0.so.0
#12 ??
#13 ??
from /usr/lib/libgthread-2.0.so.0
#14 ??
#15 ??
from /usr/lib/libgthread-2.0.so.0
#16 ??
from /lib/tls/libc.so.6
#17 __after_morecore_hook
from /lib/tls/libc.so.6
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 pthread_mutex_lock
from /lib/tls/libpthread.so.0
#32 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#33 eog_image_load
#34 eog_window_has_contents
#35 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#36 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#37 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#39 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#40 eog_wrap_list_select_right
#41 eog_wrap_list_select_right
#42 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#43 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#44 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#45 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#46 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#47 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#48 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#49 gtk_window_propagate_key_event
from /usr/lib/libgtk-x11-2.0.so.0
#50 gtk_window_propagate_key_event
from /usr/lib/libgtk-x11-2.0.so.0
#51 eog_window_get_type
#52 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#53 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#54 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#55 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#56 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#57 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#58 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#59 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#60 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#61 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#62 g_main_depth
from /usr/lib/libglib-2.0.so.0
#63 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#64 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#65 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#66 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#67 main
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0





------- Bug created by bug-buddy at 2006-02-09 09:55 -------

Comment 1 reuleaux 2006-02-09 11:38:50 UTC

this is the message I get in the xterm (stderr I guess, in German)

GThread-ERROR **: file gthread-posix.c: line 351 (): error 'Nicht genügend Hauptspeicher verfügbar' during 'pthread_create'
aborting...

translation:
'Nicht genügend Hauptspeicher verfügbar' is 'not enough RAM'

Comment 2 reuleaux 2006-02-09 12:02:37 UTC

Might be a false alarm: I just checked this with an newer eog (2.12.2)
on debian sid on a mashine with even less RAM, 256M: 
the problem seems not to occur any more, I would still like
to get some feedback: has this problem (older eog, 2.8.2) bothered 
anyone else, has it been fixed (or has it just magically disappeared)?

Comment 3 Karsten Bräckelmann 2006-02-09 21:11:26 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.


reuleaux, you are correct. This bug has been previously reported for older EOG versions (2.8.x) and was fixed. :)

Identical stacktrace as bug 165230, duplicate of bug 315147.

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

Comment 4 Karsten Bräckelmann 2006-02-09 21:14:23 UTC

The console output mentioned in comment 1 is exactly the console output noted in bug 315147, FWIW.

Thanks for providing detailed information. :)