Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

ShipIt process burning CPU on Mac #1980

Open
Labels
os: macosSpecific to macOS operating system type: imperfectionPerceived defect in any part of project
@gmofishsauce

Description

Describe the problem

Recently, I've noticed that my Mac has terrible battery life.

Today I learned that Mac users, including Arduino users, are reporting the ShipIt process burning 100% CPU endlessly. See this thread element-hq/element-desktop#647. Unfortunately, it is the type of problem where it's difficult to assign responsibility, because ShipIt is apparently used by many products, including GitHub, VSCode, and Arduino IDE.

In my case, however, the responsibility apparently lies with the Arduino IDE. I see this:

Macbook-Pro-2019:yarc jeff$ ps -efww | grep -i shipit
 501 72870 1 0 4Mar23 ?? 12946:47.14 /Applications/Arduino IDE.app/Contents/Frameworks/Squirrel.framework/Resources/ShipIt cc.arduino.IDE2.ShipIt /Users/jeff/Library/Caches/cc.arduino.IDE2.ShipIt/ShipItState.plist
 501 28553 2104 0 10:20AM ttys000 0:00.00 grep -i shipit

Mac Activity Monitor confirms, showing ShipIt using 99.8% CPU and having accumulated over 215 hours of CPU time.

To reproduce

Obviously I have no idea how to reproduce this. But this bug should remain open to track the problem until someone figures out how to reproduce and/or fix this issue.

Expected behavior

ShipIt should not consume 215 hours of CPU while continuing to run at 100% CPU.

Arduino IDE version

Arduino IDE 2.0.4

Operating system

macOS

Operating system version

Ventura 13.2.1

Additional context

Although I doubt that it matters, my Arduino project can be found at https://github.com/gmofishsauce/yarc/tree/main/ard/yarc_fw

Issue checklist

  • I searched for previous reports in the issue tracker
  • I verified the problem still occurs when using the latest nightly build
  • My report contains all necessary details

Metadata

Metadata

Assignees

No one assigned

    Labels

    os: macosSpecific to macOS operating system type: imperfectionPerceived defect in any part of project

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /