GNOME Bugzilla – Bug 758652
Crash when resizing the editor window
Last modified: 2016-01-30 22:54:25 UTC
I saw this error under the 2.8.14 version, but it appears to be still a problem for me on 2.8.16. As soon as the editor window is resized after selecting a "new" canvass, the application crashes. It is possible to continue working if you avoid resizing.
What's the editor window you're referring to? Resizing an image window in multi-window mode does not cause a crash for me, at least.
After starting the GIMP2.8.14/16 click on file->New edit the size of the canvas as required and click OK Now drag the boundary of the image window to make it larger you will receive the message: GNU Image Manipulation Program has stopped woking A problem caused the program to stop working correctly. Windows will close the program and notify you if a solutions is available.
This was a problem with the very first 2.8.14 installer, but got corrected in an update. And as I wrote, I couldn't reproduce it in 2.8.16 yet. Does it only happen if you make the window larger?
It stops working when making the window larger or smaller. I again did a fresh install of 2.8.16 and restarted the machine. Also a problem for me on this latest 2.8.16 version. I tried to leave the machine for a few minutes to settle down after opening a new canvass - to allow pageing taking place in the background to settle down before dragging the window frame, but this also did not help.
yes this happens in windows 7. gimp crashes when re sizing the window after loading an image. Message also saying about visual studio. This is what happens when re sizing and also it includes some information. http://fat.gfycat.com/WeirdCalculatingChihuahua.gif
In above comment "Problem Event Name'" is "AppHangB1". But Mostly when re sizing the window after an image loaded "Problem Event Name'" is "APPCRASH". mentioning an unhandled win 32 exception occurred in-gimp 32.exe[4376]. Above one happened once or two mostly this is what happens. http://i.imgur.com/1UoK5m2.gif
*** Bug 759326 has been marked as a duplicate of this bug. ***
*** Bug 759325 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this. 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 bug 759602 ***