{"push_id":909699468,"size":1,"distinct_size":1,"ref":"refs/heads/develop2","head":"530c57dee08e2d37bb308f265c5c7a362c6bdb8c","before":"037bcdea2775aaa647751c0e223222d14ba68af6","commits":[{"sha":"530c57dee08e2d37bb308f265c5c7a362c6bdb8c","author":{"email":"dfddabaa9af05982b01940b837a87844148069c9@ni.com","name":"Sergey Kizunov"},"message":"Fixed Windows salt-master memory leaks in logger\n\n__process_multiprocessing_logging_queue:\n- A leak was observed in this process on Windows. On Windows, creating a\nnew process doesn't fork (copy the parent process image). Due to this, we\nneed to setup extended logging inside this process. The leak was due to\nthe temp null and temp logging handlers being active which just store\nmessages but don't process them. Setting up extended logging removes\nthose handlers and fixes the leak (as well as properly dealing with\nincoming logging messages).\n\nsetup_multiprocessing_logging:\n- A leak was obversed in processes that used this on Windows. Similar\nto above, due to lack of fork, the new process will have the temp null\nand temp logging handlers enabled, causing the leak. In this function,\nremoving those handlers prevents the leak.\n\nSigned-off-by: Sergey Kizunov <sergey.kizunov@ni.com>","distinct":true,"url":"https://api.github.com/repos/skizunov/salt/commits/530c57dee08e2d37bb308f265c5c7a362c6bdb8c"}]}