GNOME Bugzilla – Bug 512707
GIMP crashes when using Move tool after scaling a layer
Last modified: 2008-10-30 20:08:52 UTC
After pasting a new layer into an image, GIMP 2.4.3 crashes if the layer is resized and then the alignment tool is selected.
Thanks for the report. I am unable to reproduce this, please be more specific. Exactly * how do you scale the layer? * how are you using the floating selection/anchor functionality here? * what dimensions of the layer and image should be used to faithfully reproduce the crash? * does the zoom level matter? * are you doing something before this? using any other tools first? etc The more details the better.
Step 1: Create a new image (400 x 300) Step 2: Paste a new layer into the image Step 3: Scale the layer BY PERCENT to 35% by 35% Step 4: Select the "move" tool I can only reproduce the crash when resizing the layer as a percentage of the original size. I am not doing any manipulation to the iamge prior to the steps I listed above.
First you said Alignment tool, now you say Move tool. What exactly do you mean? And when exactly does GIMP crash? At the moment you click on the tool icon?
Sorry... new GIMP user here. It is the Move tool, not the Alignment tool. GIMP crashes as soon as the Move tool is selected after resize the layer by a percentage of the original layer size. Please let me know if further information is required and I will try to supply.
I can't reproduce this. Is the size of the pasted layer important? How do you scale the layer?
Clayton, please answer all the question from comment #3 and also comment #5.
Here are the exact steps I'm using to reproduce this error: Step 1: Launch GIMP and create a new image (400px x 300px) Step 2: Paste a new layer into the 400x300 image. The new layer is 338x282px Step 3: Select the Scale tool and click the pasted layer Step 4: Selct Percent as the scale mode in the Scale dialog Step 5: Scale the layer to 35% x 35% of original size Step 6: Select the Move tool Step 7: GIMP crashes I've tried several different variations on the size that the layer is scaled to (40% x 40%, 50% x 50%, 80% x 70%, etc.). GIMP crashes regardless of the values selected. The bug also appears to be independent of the size of the new image that is orignally created and the size of the layer pasted into it. I've also tried pasting different image types (.gif, .jpg) as the new layer and experienced the same issue. Please let me know if more information will be of assistance.
I can't reproduce the crash following these instructions. Not with trunk nor with gimp-2-4. I assume that after step 2 you did not create a new layer out of the floating selection? Is that correct? How exactly do you select the Move tool?
I can reproduce it. It happens if I change the tools (at least the last one to the move tool) using the keyboard shortcuts. I'll attach a crash log when I'm back at my own system tonight.
Michael, can you please attach your crash log? Thanks.
Hm, another one of the cases where something is not reproducable with my own build.
Since the bug report still doesn't have a clear and detailed description on how to reproduce the problem, I am setting it to NEEDINFO until that information is eventually provided.
My crash data on this problem I only experienced after installing 2.4.4 (even after I tried uninstalling 2.4.4 and re-installing 2.4.3) Problem signature: Problem Event Name: APPCRASH Application Name: gimp-2.4.exe Application Version: 0.0.0.0 Application Timestamp: 47a071d0 Fault Module Name: libgobject-2.0-0.dll Fault Module Version: 2.14.5.0 Fault Module Timestamp: 4794e998 Exception Code: c0000005 Exception Offset: 00020fbd OS Version: 6.0.6000.2.0.0.768.3 Locale ID: 1033 Additional Information 1: ce6f Additional Information 2: 98f91a19fed4eacebd1afc68ad5cb4bb Additional Information 3: fe1f Additional Information 4: c86e3db6c6f96ee13e9a6d03d2502216
This is a duplicate of bug #515415, which in turn is a duplicate of bug #506769.Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 506769 ***