Bugs item #1891819, was opened at 2008-02-12 10:32 Message generated for change (Comment added) made by sistisette You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1891819...
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: puredata Group: v0.40.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Matteo Sisti Sette (sistisette) Assigned to: Nobody/Anonymous (nobody) Summary: too many messages to NETSEND freeze pd forever (but 0% cpu)
Initial Comment: If you send "too many" messages to netsend in zero logical time, PD immediately stops responding forever, WITHOUT eating up any cpu at all.
Attached patch illustrate the problem. Click on the "connect" message box, and then on the [bng]
Note that it only happens if netsend is connected. If not connected, it will properly output all the "error: not connected" error messages.
Tested on Windows XP, Intel Core Duo. PD-Vanilla 0.40.1
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette)
Date: 2008-02-12 12:11
Message: Logged In: YES user_id=1709568 Originator: YES
File Added: SEND.pd
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette) Date: 2008-02-12 12:11
Message: Logged In: YES user_id=1709568 Originator: YES
File Added: RECEIVE.pd
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette) Date: 2008-02-12 12:10
Message: Logged In: YES user_id=1709568 Originator: YES
please ignore the previous comment, it was incomplete and i didn't mean to send it.
I'll post the complete comment and attached files later
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette) Date: 2008-02-12 12:08
Message: Logged In: YES user_id=1709568 Originator: YES
More and more and more weird.....
Have a look at the attached SEND.pd and RECEIVE.pd
1) Open them IN TWO SEPARATE INSTANCES OF PD
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette) Date: 2008-02-12 12:07
Message: Logged In: YES user_id=1709568 Originator: YES
File Added: RECEIVE.pd
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette) Date: 2008-02-12 12:06
Message: Logged In: YES user_id=1709568 Originator: YES
File Added: SEND.pd
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette) Date: 2008-02-12 11:20
Message: Logged In: YES user_id=1709568 Originator: YES
The problem seems to be in netreceive, not netsend.
I have tried by eliminating the netreceive, and using another application to receive the data. I increased the number of message sent by a factor of 30 and no problem. Obviously netsend blocks for a considerable time, needed to send all the data (a few seconds), but then PD works normally.
Another note: the critical amount of data needed to hang PD seems to be dependent on the total size, not the number of messages (which is not surprising), and seems to be around 32 kB (something more than 32kB indeed).
May I guess it is an issue with some buffer that gets full?
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1891819...