atombender 7 hours ago

Having my app consume 300GB of virtual memory after running for a week is not ideal.

Reply View 8 replies
  • [removed] 7 hours ago
    [deleted]
    Reply View 0 replies
  • piperswe 7 hours ago

    Is it actually resident or is it just mapped but unused?

    Reply View 6 replies
    • atombender 7 hours ago

      It does not count under private memory, so I assume mapped but unused. The last time I asked Claude, it said confidently it was a bug in Swift's networking stack, which I doubt.

      Reply View 5 replies
      • DrewADesign 6 hours ago

        That’s the great thing about indiscriminately scraping the internet for knowledge.

        I’ll bet Claude was channeling some Reddit guru dripping with swagger born from knowing their understanding of coding is far more advanced than most big-shots in the field— especially impressive because they only wandered into /r/LearnProgramming for the first time several months prior.

        Reply View 2 replies
      • piperswe 5 hours ago

        Mapped but unused memory is imaginary (at least, on modern UNIX systems). It's not actually using any physical RAM.

        Reply View 1 reply
        • junon 5 hours ago

          Well, depends. Not always zero but in a good implementation not more than a few bytes per allocation, at most (if not zero).

          Reply View 0 replies