Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#238 netsend/netreceive sometimes drop data

v0.40.1
closed-fixed
nobody
puredata (318)
5
2008-02-17
2008-02-11
No

If you send a great enough number of messages throught a netsend immediately after the connection is established (for example triggered by the 1 output of netsend), the first messages are lost (and no error message issued). Netreceive receives some corrupted data, and then the last N messages sent.

The attached patch illustrates the problem.

** TEST PROCEDURE:
Click on the [connect ...( message box

** EXPECTED BEHAVIOUR:
On PD output window the following should appear:

CONNECTED: 1
DATA: bla bla 1
DATA: bla bla 2
DATA: bla bla 3
...
DATA: bla bla 1000

** OBSERVED BEHAVIOUR
The following output appears:
CONNECTED: 1
DATA: 53
DATA: bla bla 954
DATA: bla bla 955
...
DATA: bla bla 1000

====

Note that if you later click the [bng], all works as expected, i.e. no message is lost: message loss only seems to happen when too many messages are sent immediately after connection.

Discussion

  • Logged In: NO

    This DOESN'T ONLY happen when the burst of messages is sent immediately after connection.

    I have experienced message loss even sending a big burst of messages to a netsend that has been connected for a long time.

    I may send a burst of M messages and loose messages K through N with 0<K<N<M.
    In this case message N+1 is corrupted (its last part is received).

    Also, it seems that the burst doesn't need to be sent in 0 logical time to reproduce the bug. It seems it is sufficient to send enough messages in enough little time.

     
    • summary: netsend: messages sent just after connect are lost/corrupted --> netsend/netreceive sometimes drop data
    • status: open --> closed-fixed
     


Anonymous


Cancel   Add attachments