am 02.08.2002 21:51 Uhr schrieb Olaf Matthes unter olaf.matthes@gmx.de:
I've used a t_clock that gets called (clock_delay(x->x_outclock, 0)) from the child thread (in oggcast~ for example). But my externals using this method tend to crash after a while (with a segfault in pd.dll under Win2k). Sometime after a few minutes, sometimes it takes several hours. I've now deleted this functions and it seems to work. But I've lost output!
Hi Olaf, that's strange because in the upcoming thread-enabled version of flext i use the same method and did not (yet?) encounter any problems. I'll further explore that and report my experiences.
greetings, Thomas
Thomas Grill schrieb:
Hi Olaf, that's strange because in the upcoming thread-enabled version of flext i use the same method and did not (yet?) encounter any problems. I'll further explore that and report my experiences.
Well, it only happens after having called clock_delay several thousand (or even hundreds of thousands of) times. I also experienced that switching on debugging output helps. Maybe I'm just calling them to short after another when Pd just hasn't really processed the last call... debugging output needs time and thus increases the times between calls. But this is a wild guess.
Olaf