The solution posted by Dany67 is just a temporary fix, which simply disable the Proxy "Automatically detect settings" under Windows :
After enabling the Proxy "Automatically detect settings", the memory leak occurs again when starting the program : the leak will first using all memory, then swaping and filling the disk, finally the program and/or computer will crash.
Meantime, InDesign is also concerned and not fixed. The latest 64 bits version of Adobe Reader (october/november) is now also concerned ! On the other hand, Google Drive Desktop has a very similar problem.
Can you please try to find and solve the problem ? Can you also contact Avast for helping ?
As the problem could comes from a third party library / framework, and concerns more and more peoples, it would be necessary to inform Microsoft or Google.