Closed scanban closed 7 months ago
That's funny. I think your generic FFIAlloc
I think 0b2b6b76fd9b2a9ff35f764347109ad64f636d4a contains changes not actually related to the leak (probably for the better, but this should be a separate commit).
I think 0b2b6b7 contains changes not actually related to the leak (probably for the better, but this should be a separate commit).
it is, plus some simplifications/style of the code. Next should be creating of network interfaces based on interface index with multiple addresses to be on par with the Linux results.
Btw, what tool you are using on Win for detecting memory leaks ? Windows is not my primary development platform.
Hi @scanban! I can see you are also participanting in the PR opened by @njeisecke. Would you like to focus in such PR? So we all participate in the same effort?
Hi @scanban! I can see you are also participanting in the PR opened by @njeisecke. Would you like to focus in such PR? So we all participate in the same effort?
Hello @EstebanBorai, yea sure. I think that @njeisecke could get some bits from my changes if he decide to do that. And my PR then could be dropped.
Yeah, I would use the generic RAII wrapper and restore the retry counter. @scanban, would you then do a follow-up with your other changes?
Ok, #53 now also contains the @scanban changes relevant to the leak fix.
Yeah, I would use the generic RAII wrapper and restore the retry counter. @scanban, would you then do a follow-up with your other changes?
yea, sure
Removed 2 memory leaks in windows related code, added FFI output buffer management wit RAII. Removed not needed memory allocation(s)
PS. ohh, looks like @njeisecke already added same ;) Feel free to drop mine if not needed