GNOME Bugzilla – Bug 333568
gimp crash at reconnect display if new image has layermask
Last modified: 2008-01-15 13:05:58 UTC
gimp-2.2.10 crashes at reconnect display when the old image had one layer without a layermask but the new image (where the display shall be reconnected to) has a layer with layermask. The error can be triggered via image revert or via gimp-gap when stepping from one frame to another. Additional Notes: If the involved image(s) have more than one layer the error appears only in certain situations, (maybe dependent to visibility and/or layerstack position of the layer(s) having a layermask) i use gimp with gtk+-2.6.7 Example howto reproduce: 1.) start gimp-2.2 --stack-trace-mode always 2.) File->New crate a new image 320x200, RGB 3.) Open Layers Dialog and add Alpha Channel 4.) Open Layers Dialog and add Layermask (white (full opacity) 5.) File->Save AS img.xcf 6.) Open Layers Dialog and delete Layermask 7.) File->Revert GIMP crashes, and prints out the following stacktrace: gimp-2.2: fatal error: Segmentation fault
+ Trace 66714
(script-fu:445): LibGimpBase-WARNING **: script-fu: wire_read(): error hof@gimpix4:[tmp_frames] >
Reproducible with GIMP 2.3. Seems to break with a very similar stack trace.
Fixed in both branches: 2006-03-06 Sven Neumann <sven@gimp.org> * app/display/gimpdisplay.c (gimp_display_reconnect): keep a reference on the old image until the display is connected to the new one. Fixes bug #333568. * app/display/gimpdisplay-handlers.c: fixed typo in comment. * app/actions/file-commands.c: cosmetics.