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 686850 - Help system: GIMP crashes and closes without saving changes
Help system: GIMP crashes and closes without saving changes
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: General
2.8.2
Other All
: Normal critical
: 2.8
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-10-25 08:41 UTC by Olya Kozub
Modified: 2012-11-05 00:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
program freezes (182.72 KB, image/jpeg)
2012-10-25 08:41 UTC, Olya Kozub
Details
program closed (156.50 KB, image/jpeg)
2012-10-26 18:07 UTC, Olya Kozub
Details
help system settings (175.96 KB, application/octet-stream)
2012-10-29 12:47 UTC, Olya Kozub
Details
Stacktrace (469 bytes, text/plain)
2012-11-04 18:49 UTC, Max Mustermann
Details

Description Olya Kozub 2012-10-25 08:41:43 UTC
Created attachment 227230 [details]
program freezes

after you call the command Layer -> New Layer -> Help,  and then immediately click Cancel (one or two times), the program freezes; then you should close it (because there are no answers anymore), program closed and the changes are not saved
Comment 1 Michael Natterer 2012-10-26 15:59:24 UTC
Can anyone reproduce this?
Comment 2 Olya Kozub 2012-10-26 18:07:52 UTC
Created attachment 227380 [details]
program closed
Comment 3 Olya Kozub 2012-10-26 18:08:23 UTC
I've found extra details: GIMP won't respond and will be closed by the system if I  click Help option in any ways.
Comment 4 Max Mustermann 2012-10-28 17:18:30 UTC
I couldn't reproduce this with GIMP 2.8.2 on Win 7, 32 bit. 
It seems your help system is broken. 
Can you please attach a screenshot of your help system settings you find in Edit/Preferences/Help system?
Do you use the official GIMP Windows build from gimp-win.sourceforge.net? If no, please try this and report back.
This behaviour could also be a problem of a non-working internet connection. Is your computer connected to the internet and access from GIMP help system not blocked by a firewall when the error occurs?
Which browser is installed on that computer?
Comment 5 Michael Schumacher 2012-10-28 17:35:23 UTC
I couldn't reproduce this either - but depending on the state of the GIMP setup on the system, there may be different dialogs to cancel - i.e. help to be displayed in web-browser with local help installed, help to be displayed in help-browser with local help installed, ...

The screen-shot of the help options should clear this up, but we'd still have to know which dialog is being canceled.
Comment 6 Olya Kozub 2012-10-29 12:47:15 UTC
Created attachment 227526 [details]
help system settings

GIMP downloads from www.gimp.org. I use Google Chrome browser and internet connestion is ok.
Comment 7 Max Mustermann 2012-11-04 18:49:48 UTC
Created attachment 228044 [details]
Stacktrace

Thank you. 
Your GIMP configuration is set up to use the internal help browser to show the help. What happens if you set the listbox 'Help browser to use' to 'Web browser' and try accessing the help after closing the dialog?

I also tested with the internal help browser and the steps from your original report on a new image. GIMP crashes sometimes, indeed. Maybe the attached stacktrace from DrMinGW can tell us more, although it's very terse...
Comment 8 Michael Natterer 2012-11-04 20:39:30 UTC
I can reproduce that on linux too, with a proper stack.
Comment 9 Michael Natterer 2012-11-05 00:18:01 UTC
Fixed in master and gimp-2-8:

commit 4f2d0c9ed194d3a840cdcb985d6b05db9d3b2a66
Author: Michael Natterer <mitch@gimp.org>
Date:   Mon Nov 5 01:12:21 2012 +0100

    Bug 686850 - Help system: GIMP crashes and closes without saving changes
    
    When gimp_plug_in_close()ing a plug-in (such as when cancel is
    clicked), make sure we don't leak the proc_frames of all temporary
    procedures the plug-in is currently running. By properly disposing the
    GimpPlugInProcFrame, the progress window and its cancel button in
    above bug get destroed on first click, and the user has no chance of
    trying to kill an already finalized plug-in again.
    (cherry picked from commit eac70cc513ef3a073b6f3d2fe3794d13d97b204c)

 app/plug-in/gimpplugin.c |   12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)