[HN Gopher] Finding a VS Code Memory Leak
       ___________________________________________________________________
        
       Finding a VS Code Memory Leak
        
       Author : brucedawson
       Score  : 31 points
       Date   : 2025-10-09 20:27 UTC (2 hours ago)
        
 (HTM) web link (randomascii.wordpress.com)
 (TXT) w3m dump (randomascii.wordpress.com)
        
       | brucedawson wrote:
       | In 2021 I found an invisible memory leak in a tool (VS Code) that
       | I have never used. This is the story of how.
        
       | anonymousDan wrote:
       | Re the last wish, isn't that exactly what ulimit is for?
        
       | anonymars wrote:
       | > Sometimes I think it would be nice to have limits on resources
       | in order to more automatically find mistakes like this
       | 
       | I was actually fairly disappointed when Visual Studio (not code)
       | went to 64-bit. Because I knew its memory usage was now going to
       | be unconstrained. Still way better than the unapologetic gluttony
       | of Rider but experiences showed it to be a bit leaky over time
       | (tip: Ctrl-Alt-Shift-F12 twice does a full garbage collection
       | https://learn.microsoft.com/en-us/visualstudio/ide/visual-st...)
       | 
       | Also remember that all your references (pointers) are going to
       | double in size so right off the bat it will use more, potentially
       | a lot more depending on how reference-heavy your data is
        
       ___________________________________________________________________
       (page generated 2025-10-09 23:00 UTC)