kostko / libcurvecpr-asio Goto Github PK

CurveCP session seems to hang in some cases, not closing correctly or simply hanging while transferring data. The problem might be related to packet reordering in libcurvecpr (there already were other problems with it), but this has not yet been confirmed.

Sometimes when the issue occurs, there appear to be timeouts that increase the Chicago-derived wr_rate to absurdly high values, sometimes even overflowing the wr_rate counter (this is in libcurvecpr) -- this causes the session to hang as the write rate becomes insanely low.

When compiling code using libcurvecpr-asio, I get a number if warnings about conversions from uint64_t and size_t with possible loss of data.
I was wondering why size_t is not used consistently here instead of uint64_t and size_t getting mixed, is there a specific reason for this ?

The 4 warnings are:

2>C:\libs\libcurvecpr-asio\include\curvecp/detail/impl/session.ipp(219): warning C4244: 'initializing' : conversion from 'uint64_t' to 'size_t', possible loss of data
2>C:\libs\libcurvecpr-asio\include\curvecp/detail/impl/session.ipp(294): warning C4244: 'initializing' : conversion from 'uint64_t' to 'int', possible loss of data
2>C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\algorithm(4141): warning C4244: 'argument' : conversion from 'uint64_t' to 'const size_t', possible loss of data
2>C:\libs\libcurvecpr-asio\include\curvecp/detail/impl/session.ipp(335): warning C4244: 'initializing' : conversion from 'uint64_t' to 'int', possible loss of data