Did Harper Desktop cause me to run out of memory?

I think I only killed Devin (Windsurf's new name) before taking this screenshot. I have 16GB, most you could order on an OG M1 MacBook Air and I do have situations like this once a week or so without running Harper Desktop, so it's not certain. But 21.3GB is ***a lot***, it's double what Chrome is using, and I have 46 tabs open across 8 windows.

I just upgraded to the newly released 2.6.0 and tested Desktop this morning and left it running. My laptop was fine during breakfast but when I reached the café 10/15 minutes later it was so bogged down that I almost couldn't sign in, and when I did manage it, I was confronted with the out-of-RAM dialog.

Harper is my prime suspect, but not the only one.

Start by reproducing the reported memory spike with Harper Desktop 2.6.0 on the author's 16GB M1 MacBook Air while monitoring memory usage. Compare runs with Harper Desktop running and not running, and use the results to determine whether Harper is responsible for the out-of-memory condition.

Written by the indexing model from the issue text.