Potential leak of handles and memory

[tovine]

It seems like something in the way you (or one of your dependencies) use java causes it to over time leak file handles, which in turn makes windows expand the virtual memory page table and eat all available RAM...

Please see these two comments on this issue for more details:
microsoft/vscode#50280 (comment)
microsoft/vscode#50280 (comment)

[angelozerr]

Please give us usecase to reproduce the problem. Thanks Le lundi 11 février 2019, Torbjørn <notifications@github.com> a écrit :

…

It seems like something in the way you (or one of your dependencies) use java causes it to over time leak file handles, which in turn makes windows expand the virtual memory page table and eat all available RAM... Please see these two comments on this issue for more details: microsoft/vscode#50280 (comment) <microsoft/vscode#50280 (comment)> microsoft/vscode#50280 (comment) <microsoft/vscode#50280 (comment)> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#108>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB17s7xtQzoT-IogyI58Oo0szHwLyqe0ks5vMXGKgaJpZM4a0MkJ> .

[tovine]

0. Open Windows Task Manager and make sure the "Handles" column in the "Details" tab is visible (right-click the headings, click "Select columns" and find it in the list).
1. Open a XML file in VSCode
2. In Task Manager, find VSCode, expand it and find the java.exe (in my case "OpenJDK Platform binary")
3. Right click it and select "Go to details"
4. Sort the list by "Handles" and watch java.exe make its way up towards the top

The number of handles seems to be slowly and steadily increasing; in my case it seems to be about 2-3 handles every few seconds, but leave it overnight or for a few days and it is likely to reach the 100k's range...

[snjeza]

Related issue - redhat-developer/vscode-java#789

[snjeza]

I can still reproduce the issue with JDK 11.