www.delorie.com/archives/browse.cgi | search |
I have just tried this on another machine with Cygwin - no leaks. OK, so it is not Cygwin - my bad, but I'm glad. Just to test, I have made a script for WIndows' cmd.exe: @echo off set c=1 :loop cmd /c echo > nul echo %c% set /a c=%c%+1 if %c%==123456 goto end goto loop :end Leaks... Not so fast as bash, but that is because executing "cmd /c" takes much longer. It leaks approximately the same considering the numbers represented by %c%. So, forking in Windows itself (not Cygwin) it apparently is the whole problem - in fact, as you mentioned - it's probably some other process (AV, whatever) messing up with Windows' normal CreateProcessA, as bash politely explained - and I assume the above script will also - didn't finish yet :(. Sorry for bugging you for something that apparently is not Cygwin-related - should have tested more. -- View this message in context: http://www.nabble.com/Huge-memory-leak%2C-probably-related-to-making-new-processes-tf4557470.html#a13019145 Sent from the Cygwin Users mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |