[PD] pd becomes unresponsive but does not eat cpu

[matteo sisti sette]

I could finally isolate it.

It is a bug in netsend (again!), not print.

If you send too many message to netsend in 0 logical time, pd freezes
and stops responding, but without eating up CPU.

Here's a simple patch that reproduces it.
I guess the critical quantity of messages may be platform dependent
(or not), so if it does not reproduce the bug try increasing the
number in the message box.



2008/2/11, matteo sisti sette <matteosistisette at gmail.com>:
> Hi,
>
> Does anyone know what kind of errors may cause PD to become completely
> unresponsive (i.e.: you click on any GUI object and nothing happens,
> ctrl+e does not change cursor, clicking on any object doesn't open it,
> pd's window won't close, etc) but without consuming any CPU at all
> (0%)???
>
> It's something triggered by something in my patch, but as usual I am
> not able to isolate it, as all tests with small quantities of things
> always worked and never had any error, and just when things get bigger
> (only a matter of quantity: more instances of the very same things)
> something weird happens....
>
> Windows XP here.
>
>
> What if a message tree becomes HUGE not in depth (which would give a
> stack overflow) but in "breadth"? A part from the time needed to
> execute it (if that was the problem, pd would hang consuming a lot of
> cpu), is it possible that it gets just too big and everything breaks
> and stop working without triggering a stack overflow or whatever
> error? Or must it be something else?
>
> Thanks,
> m.
>
> --
> Matteo Sisti Sette
> matteosistisette at gmail.com
> http://www.matteosistisette.com
>


-- 
Matteo Sisti Sette
matteosistisette at gmail.com
http://www.matteosistisette.com
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bug_netsend.pd
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20080212/245d08eb/attachment.txt>