When the memory overload happens, the entire mac freezes. I can’t go to Activity Monitor, nor switch to the terminal. I can’t run a dump or literally do anything other than stare at a spinning beachball until my screen goes blank and the mac crashes.
Before this happens, Mac opens up a little window showing applications are frozen, and their memory usage, with the only option to force kill. Cursor is the main culprit Although I understand you are saying that it’s more likely some extension rather than cursor itself.
However, given that cursor is the host for these extensions, it seems reasonable to me that you could enact some kind of data collection and enforcement of CPU and memory usage allocated to extensions or sub-processes that are started by extensions.
The reason I think this is related to gopls is that the one time I was able to kill Before going into a spiral, I had run top -o mem and saw 5-6 gopls processes consuming a lot of memory all parented by a “Cursor Helper (Plugin)” process that was not killed along with the main Cursor window.
Here are some other threads: