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 356904 - Spyrogimp Crash on Windows
Spyrogimp Crash on Windows
Status: RESOLVED DUPLICATE of bug 359538
Product: GIMP
Classification: Other
Component: Plugins
2.3.x
Other Windows
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-09-20 13:30 UTC by jbaker
Modified: 2008-01-15 14:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jbaker 2006-09-20 13:30:24 UTC
Steps to reproduce:
1. New Image
2. Filters render Spyrogimp
3. Click the browse button for brush dialog


Stack trace:
I could not find any instructions here for obtaining a stack trace on windows...

If someone would point me in the right direction I will try to get one...

Other information:
Seems to be windows only - works fine on ubuntu with current cvs...

on windows the plug-in runs fine and will execute as long as you don't hit the browse button....
Comment 1 jbaker 2006-09-20 13:31:06 UTC
sorry - Windows XP, with SP2
Comment 2 Sven Neumann 2006-09-20 14:22:26 UTC
You didn't tell us what happes when you click the browse button.
Comment 3 jbaker 2006-09-20 15:26:40 UTC
oh - sorry... 

after the click,

Spyrogimp totally freezes... It makes it to the point where I can see the window with "Script-Fu brush select" as the title, but no content... at this point Gimp itself is locked...

when I hit the close button for the script/plug-in, I get the standard Windows "This program is not responding message" - so end task...

Sometimes it completely crashes Gimp... Othertimes it just closes the script/plugin window and gives control back to Gimp. From that point Gimp seems to be working correctly, but it's not, It always completely crashes out once you create a new image...
Comment 4 Michael Schumacher 2006-10-13 23:06:07 UTC
Maybe the same problem as in bug #359538.
Comment 5 Sven Neumann 2006-10-16 12:43:11 UTC

*** This bug has been marked as a duplicate of 359538 ***