Ales Zemene wrote:

wow, sending destroy to gemwin mostly causes crash of whole pc. only switching rendering off first, sometimes helps. Sometimes. Crashing even on simple example patch curve.pd. Hard to reproduce since it needs restart machine, i'd like some hints where to look for problems and what is actualy happening. Did not find anything suspicious in logs.

2.6.11.6 Pentium III MHz : 1004.257 nVidia GeForce4 Pd version 0.38.4 GEM: ver: 0.90 GEM: compiled: Sep 16 2004

unfortunately this is a known issue.

i have committed a quick fix to the CVS a while ago, that does not destroy the X-context when doing a "destroy". to do it by hand, just comment out (or remove) the line "XCloseDisplay(info.dpy);" at the end of Base/GemWinCreateXWin.cpp

this way, you can only create/destroy the gemwindow a finite number of times (don't know, probably 20 to 50 times); then you have to restart pd. i think this is due to the double context Gem is creating, and i think this is only there for historic reasons to get the Voodoo3 cards running. i'd like to remove this part of the code anyhow, but don't know when.

mfg.asd.r IOhannes