On 07/15/2010 05:59 PM, Hans-Christoph Steiner wrote: > > On Jul 15, 2010, at 11:07 AM, IOhannes zmölnig wrote: > >> On 07/15/2010 04:46 PM, Hans-Christoph Steiner wrote: >>> >>> >>> The vwait timeout would not be needed if we can rely on 'pd' to actually >>> fully die when it exits/crashes. On Mac OS X at least it is often >>> doesn't completely crash and the process just sits there doing who knows >>> what. If this happens on startup, pd-gui's exec call will not return, >>> and pdtk_pd_startup won't be called and pd-gui will just sit and wait >>> forever, giving us a zombie pd-gui. The vwait stuff wouldn't be needed >>> if we can rely of pd to exit completely on all platforms. Just removing >>> the vwait stuff is just replacing one problem with another. >> >> sure. >> i'm only talking about the race-condition. >> whether the vwait is there for other things is entirely beyond my scope. >> >> iirc, this is the title of this thread as well. > > So you were seeing something like Tcl/pd-gui pegging the CPU when > getting stuck in a loop? Or was it that pd-gui was sitting there > waiting doing nothing?
no, pd-gui was there, pd was there, but i had not a single entry in the audio/midi API list. i couldn't select the backend. i heard nothing. pd was working fine. fgmasrd IOhannes
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
