Edit: No reason might seem excessive. It’s a TypeScript project and I was working on components that got imported everywhere so I might understand why the sizes needed to be updated, but it’s not a BIG project, it still doesn’t make sense to eat all the CPU.

Resolution

  1. Navigate to Cursor’s extension management interface
  2. Locate and disable (I also uninstalled) the “Import Cost” extension
  3. Restart Cursor

For verification, monitor CPU usage through Activity Monitor before and after implementing the fix. Command cursor --status might also help but I discovered it way too late.

Enjoy your new low energy impact Cursor !

Reference: Cursor Issue #1703

Note: This issue affected Cursor versions prior to potential patches. Check the GitHub issue for the latest status.

By Romain

Leave a Reply

Your email address will not be published. Required fields are marked *