On 09/10/2015 06:08 PM, Ashish wrote: > > I've server developed in libuv 1.0.0 and runs on Windows 8 > > What has been observed is that at some random time (yes, almost randomly > & not always. but especially when there were thousands of clients > connected and sending asynchronous requests to the server) > server keeps allocated lots n lots of memory (around 300 to 500 megabytes). > > After spending few hours of debugging what I found that this memory gets > freed in some time after I call uv_close but just before I get its callback. > > So makes me think it allocated and freed up that memory somewhere inside > libuv. > > Any idea why this could happen and solution? > > (Unfortunately I cannot narrow it down to produce smallest working code > to paste here. Because its too complex to narrow down and extract the code.) >
libuv doesn't keep a specific chunk of memory for each connection around. When a connection is closed, the underlying sockets are closed and so on, that's all. It's very hard (if not impossible) to guess what's wrong solely based on your description, sorry. One thing I do recommend, however, is to update libuv to 1.7.3. Tons of bugfixes have happened since 1.0.0 (even though I don't recall fixing leaks) and since we follow semver you shouln't have any problem. Regards, -- Saúl Ibarra Corretgé bettercallsaghul.com -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
