Closed GoogleCodeExporter closed 9 years ago
I think this is not the ssl lib issue.
The same issue on POSIX socket (nacl_io) send/recv in blocking mode vs
non-blocking.
Without using SSL, just straight Posix send/recv, the recv() is starving after
socket calls. The recv() is choking for a while
recv() try=3218 connection.js:266
recv() return=3218 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=6333 connection.js:266
recv() return=1437 connection.js:266
recv() try=4896 connection.js:266
recv() return=4896 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=6494 connection.js:266
recv() return=6494 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=5947 connection.js:266
recv() return=1437 connection.js:266
recv() try=4510 connection.js:266
recv() return=4510 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=6056 connection.js:266
recv() return=1437 connection.js:266
recv() try=4619 connection.js:266
recv() return=4619 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=6200 connection.js:266
recv() return=1437 connection.js:266
recv() try=4763 connection.js:266
recv() return=4763 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=6028 connection.js:266
recv() return=2877 connection.js:266
recv() try=3151 connection.js:266
recv() return=3151 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=5252 connection.js:266
recv() return=1437 connection.js:266
recv() try=3815 connection.js:266
recv() return=3815 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=5728 connection.js:266
recv() return=2877 connection.js:266
recv() try=2851 connection.js:266
recv() return=2851 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=5404 connection.js:266
recv() return=1437 connection.js:266
recv() try=3967 connection.js:266
recv() return=3967 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=4881 connection.js:266
recv() return=4881 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=4307 connection.js:266
recv() return=4307 connection.js:266
recv() try=2 connection.js:266
recv() return=2 connection.js:266
recv() try=1 connection.js:266
recv() return=1 connection.js:266
recv() try=2898 connection.js:266
recv() return=2898 connection.js:266
recv() try=2 connection.js:266
==> no return from recv()
Original comment by mele3...@gmail.com
on 12 Jan 2014 at 5:48
Do you have a source code sample that demonstrates this issue?
Original comment by sbc@chromium.org
on 6 Feb 2014 at 11:23
[deleted comment]
Is this still an issue? We've make a few fixes to the nacl_io socket code
recently so I would hope that it was fixed.
Original comment by sbc@google.com
on 19 Jun 2014 at 6:18
This should be fixed now.
Original comment by sbc@google.com
on 1 Oct 2014 at 4:26
Original issue reported on code.google.com by
mele3...@gmail.com
on 19 Dec 2013 at 1:30