GNOME Bugzilla – Bug 587782
crash in GNU Image Manipulation Program: Using all the ram and sw...
Last modified: 2010-05-24 23:28:56 UTC
What were you doing when the application crashed? Using all the ram and swap memory with three big files. Distribution: openSUSE 11.1 (x86_64) Gnome Release: 2.26.2 (null) (SUSE) BugBuddy Version: 2.27.1 System: Linux 2.6.27.23-0.1-default #1 SMP 2009-05-26 17:02:05 -0400 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Gilouche GTK+ Modules: gnomebreakpad Memory status: size: 1699098624 vsize: 1699098624 resident: 767721472 share: 14266368 rss: 767721472 rss_rlim: 18446744073709551615 CPU usage: start_time: 1246739302 rtime: 36650 utime: 32094 stime: 4556 cutime:29631 cstime: 1199 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gimp-2.6' [?1034h(no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f3e04426950 (LWP 1524)] [New Thread 0x7f3e04c27950 (LWP 1522)] (no debugging symbols found) 0x00007f3e0a0ff5af in waitpid () from /lib64/libpthread.so.0
+ Trace 216322
Thread 1 (Thread 0x7f3e0ea67780 (LWP 1518))
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed ** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed ** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed ** GLib **: gmem.c:136: failed to allocate 16384 bytes ----------- .xsession-errors (12 sec old) --------------------- ** (gimp-2.6:1518): WARNING **: Failed to set operation type gegl:brightness-contrast, using a passthrough op instead ** (gimp-2.6:1518): WARNING **: Failed to set operation type gegl:nop, using a passthrough op instead ** (gimp-2.6:1518): WARNING **: The failing op was 'gegl:nop' this means that GEGL was unable to locate any of it's plug-ins. Try making GEGL_PATH point to the directory containing the .so|.dll files with the image processing plug-ins, optionally you could try to make it point to the operations directory of a GEGL sourcetree with a build. (gimp-2.6:1518): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed (gimp-2.6:1518): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed GLib-ERROR **: gmem.c:136: failed to allocate 16384 bytes aborting... --------------------------------------------------
Hi and thanks for the bug report! From the stack trace, it can be seen that the crash occured when you pressed Ctrl + C. What is the step-by-step instruction on how to reproduce this? Thanks!
We are waiting for feedback here.
1. Have a computer with few memory (1gb or less) and with swawp off. 2. Open or create a big image, like a 600dpi scanned photo. 3. Start editing, apply filters, copy and cut, on a time the computer will crash.
(In reply to comment #0) > What were you doing when the application crashed? INSERTING A PIC (JPEG) IT SAYS THERE IS A FILE ERROR FOR JPEG. > Using all the ram and swap memory with three big files. > Distribution: openSUSE 11.1 (x86_64) > Gnome Release: 2.26.2 (null) (SUSE) > BugBuddy Version: 2.27.1 > System: Linux 2.6.27.23-0.1-default #1 SMP 2009-05-26 17:02:05 -0400 x86_64 > X Vendor: The X.Org Foundation > X Vendor Release: 10502000 > Selinux: No > Accessibility: Disabled > GTK+ Theme: Gilouche > Icon Theme: Gilouche > GTK+ Modules: gnomebreakpad > Memory status: size: 1699098624 vsize: 1699098624 resident: 767721472 share: > 14266368 rss: 767721472 rss_rlim: 18446744073709551615 > CPU usage: start_time: 1246739302 rtime: 36650 utime: 32094 stime: 4556 > cutime:29631 cstime: 1199 timeout: 0 it_real_value: 0 frequency: 100 > Backtrace was generated from '/usr/bin/gimp-2.6' > [?1034h(no debugging symbols found) > [Thread debugging using libthread_db enabled] > [New Thread 0x7f3e04426950 (LWP 1524)] > [New Thread 0x7f3e04c27950 (LWP 1522)] > (no debugging symbols found) > 0x00007f3e0a0ff5af in waitpid () from /lib64/libpthread.so.0
And that's the same problem as the initial report?
That was a long timea ago, I truly don't renember. Maybe I opened some JPEG file or saved some, I was multitasking so I can't say. But I'm certainly that this things happens when I'm editing big files with swap off, as I said.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!