fix how? what was wrong with your file? having same issue, also using tailwind 4 could be that
Hey, the Activity Monitor shows that the consumption is coming from extensions. Try opening the Process Explorer to identify the problem there.
If I remember it right. It was because CSS color variable references in the new CSS file that were auto generated by the Tailwind upgrade CLI from the old Tailwind config file. Just to make it conform with the css standard to solve.
1 Like
This is such an underrated comment. Thanks for providing the actual answer!
This whole thread has taught me the following:
- The runaway memory leak is because of extensions, a specific one(s)
- VS Code has a built-in tool to find the extensions that leak (summon it in the Command Palette, searching for “extension bisect”, and go through the steps
- The Zain json extension was at fault in my case, disabling it brought stability back.
Before:
Disabled this one:
After:
1 Like
The same issue is here, and I found it’s chat history related, one of my history brings CPU up to 140% on Mac M3, and all UI has no response, and then Cursor crashed a few times.
And important, reinstall Cursor dmg has no help at all, it’s local history related.
VSCode is notoriously garbage when it comes to resources utilization, the fact that Microsoft decided to use electron underneath is a travesty.
1 Like