[GEM-dev] [ pd-gem-Bugs-2808389 ] linux/radeon: Destroying gemwin crashes Pd

[SourceForge.net]

Bugs item #2808389, was opened at 2009-06-18 06:41
Message generated for change (Settings changed) made by zmoelnig
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=2808389&group_id=64325

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: rendering (e.g. display)
Group: None
>Status: Closed
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: linux/radeon: Destroying gemwin crashes Pd

Initial Comment:
Destroying gemwin crashes Pd.

Description;
-put object gemwin
-connect message 'create' to it
-connect message 'destroy' to it
-click create (creates gem window)
-click destroy (closes gem window and *crashes Pd*)

ATI Mobility Radeon X1350
Ubuntu 8.04


regards,
Vasja Progar

----------------------------------------------------------------------

Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-01-12 06:28

Message:
like with #2807707 i cannot reproduce the problem here on debian/x86_64
(wheezy/sid) with linux-3.1.0-1-amd64 and fglrx-1:11-12-1, running on an
"ATI Technologies Inc Wrestler ™Radeon HD 6310]"

does the problem still exist?

----------------------------------------------------------------------

Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2011-03-12 09:49

Message:
thanks matju for your comments.
however, this (stack corruption due to window destruction within a callback
from the window) is something that (to the  best of my knowledge) is a
problem fixed in Gem for several generations now.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2011-03-12 07:50

Message:
btw i'm only saying that if that's the crash due to destroying the window
as a direct reaction to [gemhead] or [gemmouse]. if the crash has a
different cause, nevermind. (i write again because i realised only after
the crash that it's probably unrelated.)

and Vasja should post a version number (or more precisely, svn revision
number or date)

—matju

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2011-03-12 07:45

Message:
i recommend destroying the gemwin using a clock_new() to ensure that there
are no dangling pointers left on the stack. now if only the canvases would
also do this, to prevent crashes during dynamic patching...
—matju

----------------------------------------------------------------------

Comment By: Cyrille Henry (nusmuk)
Date: 2011-03-12 01:38

Message:
This bug is still present on ubuntu 10.10,  ATI Radeon 5770, GEM from SVN.
commenting line 1042 of GemMan (gemWinMakeCurrent(constInfo)) fix the
problem.
I did not find any problem due to this hack.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=2808389&group_id=64325