Closed Esteban-Rocha closed 5 years ago
That actually makes sense. We use a language server which runs in the background and keeps a cache of all the css files in your workspace so that it can perform quick lookups when you Peek.
Hey! Thanks for your reply, and dammn! that's almost a GB there only on cache, is there a way to filter or exclude certain folders so the amount of RAM does not peak up so much?
Any updates or thoughts on this? Maybe introduce a setting where the user could specify the scope they'd like to be cached.
Hopefully in future releases this ext. will implement such setting, I had to stop using this some months ago because it's unacceptable for me for a single ext to have 1GB ~ ram allocated, even so I'll love to use it again if this is fixed.
Extension has a memory leak, I was actually doing 0 css related work and still it eats the RAM.
Version 1.19.2 Commit 490ef761b76b3f3b3832eff7a588aac891e5fe80 Date 2018-01-10T15:57:21.071Z Shell 1.7.9 Renderer 58.0.3029.110 Node 7.9.0 Architecture x64