Hello. I've been using this extension for a couple of days and I've so far encountered VS Code force closing due to my PC running out of memory. If you look at the screen recording I included below you can tell in the system monitor window, VS Code's memory usage keeps increasing. ("Bellek" is the memory usage)
When I disable the extension it goes back to normal, and when I re-enable it, the memory usage starts to increase again. In the video I have some other extensions installed too but I got the same result when I tried it with all of them disabled. The speed at which it keeps increasing memory usage is very severe.
I can see the memory usage increase through VS Code's Process Explorer as well, next to the extensionHost section:
It'd be great to see if you or anyone else can replicate the problem. I am on VS Code version 1.93.1 (latest rpm from Microsoft) and Fedora 41 (pre-release).
I have a feeling this may be caused by the FileSystemWatcher watching too many files. Is it also reproducible in a smaller project that has less files?
Hello. I've been using this extension for a couple of days and I've so far encountered VS Code force closing due to my PC running out of memory. If you look at the screen recording I included below you can tell in the system monitor window, VS Code's memory usage keeps increasing. ("Bellek" is the memory usage)
https://github.com/user-attachments/assets/af2391d2-0924-4e21-8b10-360ed460e47d
When I disable the extension it goes back to normal, and when I re-enable it, the memory usage starts to increase again. In the video I have some other extensions installed too but I got the same result when I tried it with all of them disabled. The speed at which it keeps increasing memory usage is very severe.
I can see the memory usage increase through VS Code's Process Explorer as well, next to the extensionHost section:
It'd be great to see if you or anyone else can replicate the problem. I am on VS Code version 1.93.1 (latest rpm from Microsoft) and Fedora 41 (pre-release).