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 370423 - Gimp crashes when copying huge image file sections (e.g. 2592x1944)
Gimp crashes when copying huge image file sections (e.g. 2592x1944)
Status: RESOLVED DUPLICATE of bug 172881
Product: GIMP
Classification: Other
Component: General
2.2.x
Other Linux
: High critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-11-04 10:49 UTC by Uwe Fischer
Modified: 2008-01-15 13:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Uwe Fischer 2006-11-04 10:49:05 UTC 
Steps to reproduce:
1. open image with rather high resolution (e.g. 2592x1944)
2. Select a huge image section
3. Edit --> Copy
4. Application crashes (reproducible)


Stack trace:
fi@fischilinux2:~> gimp --sync
sending pixbuf data as 'image/png' (png)
sending pixbuf data as 'image/bmp' (bmp)
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 367593 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(script-fu:8550): LibGimpBase-WARNING **: script-fu: wire_read(): error

Other information:
(SUSE Linux 10.0 standard istallation on x86 with all security updates, status: Oct 2006)
Comment 1 Raphaël Quinet 2006-11-04 15:47:41 UTC 
Thanks for taking the time to report this bug.
Without a "real" stack trace from the crash it's very hard to determine what caused it. It was right for you to run gimp with --sync, but it would be even more useful to have the stack trace from a debugger so that we can see in which part of the code the X error occurs. Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Sven Neumann 2006-11-04 15:54:34 UTC 
You are using Klipper, aren't you?
Comment 3 Uwe Fischer 2006-11-04 17:08:39 UTC 
Thanks for keeping "on track".

Unfortunately I have difficulties in generating complete "stack traces". I installed all the debugging packets (provided by my SUSE distro (full install)), but a kind of "bug buddy" pop up does not start. - I will try again tonight and tomorrow.

And by the way, yes, I do have KDE running and Klipper as "clip board" in my systray. But I did not use it. Any special hint about it? Shall I switch it off?

Thanks,
Uwe
Comment 4 Uwe Fischer 2006-11-04 17:15:17 UTC 
Quick update:

Sven, many thanks for the hint with "Klipper". Switching off "Klipper" in my KDE systray does have two advantages:

1. Gimp does not crash anymore! :-)
2. Copying is much faster (do not see the clock symbol anymore)!

Do you still want me to send the complete stack trace (which is hard for me to generate)?

Thanks,
Uwe
Comment 5 Michael Natterer 2006-11-04 18:00:34 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 172881 ***
Comment 6 Sven Neumann 2006-11-04 23:34:42 UTC 
See http://svenfoo.geekheim.de/index.php/2005-06-18/why-klipper-is-bad/ for an explanation of the problem.