Thanks for the heads up Thiago! On Feb 11, 2016 12:43, "Thiago Padilha" <[email protected]> wrote:
> Saúl > > I think I've experienced the same problem once in Neovim, but ended up > ignoring it since I couldn't find the source of the leak. > > As far as I can remember, the problem only happened when compiling with > gcc, so it could be a compiler bug. I'm not entirely sure about this > though, as I didn't investigate much. > > On Thu, Feb 11, 2016 at 6:01 AM Saúl Ibarra Corretgé <[email protected]> > wrote: > >> Hi, >> >> On 09/02/16 17:57, Vigith Maurice wrote: >> > Hello, >> > >> > I am quite new to libuv, so please pardon my newbie question. >> > >> > I am seeing a memory leak when i do uv_spawn for which the options.file >> > doesn't exist. I do know if we use >> > uv_strerror http://docs.libuv.org/en/v1.x/errors.html#c.uv_strerror it >> > will leak for unknown error codes, but this is a known error code (even >> > with uv_strerror commented out i still see the same leak). >> > >> > More Context: I am writing a light weight remote execution program >> > (daemon), since i am getting small memory leak my code is core dumping >> > if i hit it hard with concurrent requests (if i comment out the test >> > case which caused uv_spawn to fail, then i am all good). >> > >> > I am using *libuv-1.8.0* >> > >> >> [snip] >> >> I went through process.c (a quick pass) and couldn't find an exit point >> which wouldn't free the pipes array :-( Also, for some reason the leak >> only shows up on Valgrind when I run it with --show-leak-kinds=all, and >> it masks them as reachable :-O >> >> (This is on OSX, FWIW) >> >> >> ==50479== 24 bytes in 1 blocks are still reachable in loss record 16 of 85 >> ==50479== at 0x10003FEBB: malloc (in >> >> /usr/local/Cellar/valgrind/3.11.0/lib/valgrind/vgpreload_memcheck-amd64-darwin.so) >> ==50479== by 0x100003D23: uv__malloc (in ./footest) >> ==50479== by 0x1000116CA: uv_spawn (process.c:418) >> ==50479== by 0x1000015A8: main (in ./footest) >> >> I'll have a closer look just in case though. >> >> >> Cheers, >> >> -- >> Saúl Ibarra Corretgé >> http://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 https://groups.google.com/group/libuv. >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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 https://groups.google.com/group/libuv. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
