Mac: "ShipIt" using 99% CPU

[Behodar]

Steps to reproduce

I've only seen this happen once, so I'm not sure how much help it'll be, but I figured I should report it anyway.

My Intel iMac is usually quiet, but the fans had been running at a low speed for an hour or so. Eventually I looked in Activity Monitor and found that "ShipIt" was using 99% CPU.

I did Inspect Process on ShipIt, and under Open Files I could see that it had some Element files open. I then quit Element, which didn't make ShipIt go away.

Next, I quit (not force quit) ShipIt via Activity Monitor. This made Element start up again. Quitting it a second time resulted in the fans spinning back down, and I've subsequently opened Element again and it's still being quiet.

Outcome

What did you expect?

I don't know what ShipIt is, but I wouldn't expect it to use 99% CPU for an extended period.

What happened instead?

See above.

Operating system

macOS 12.3.1

Application version

Element 1.10.13

How did you install the app?

From https://element.io/get-started

Homeserver

matrix.org

Will you send logs?

Yes

[Behodar]

rageshake.tar.zip

[turt2live]

It looks like ShipIt is an iOS development tool - were the files it was holding open related to Element Desktop or Element iOS?

[Behodar]

The files were part of /Applications/Element.app, the desktop Mac version. I didn't think to save the actual list of open files.

[Behodar]

Digging a little deeper, ShipIt is included inside Element: Contents/Frameworks/Squirrel.framework/Versions/A/Resources/ShipIt.

[turt2live]

it's also not an iOS development tool specifically - looks like an image compressor actually.

[Behodar]

Hmm... I had sent a PNG image around the time that the issue occurred, but I've just retested with the same image a couple of times and the problem has not reoccurred.

[dbkr]

Shipit == Squirrel, ie. our update framework, so somehow this has apparently gone awry. Unfortunately there will be nothing in the rageshake logs, although if this happens again, squirrel has logs in ~Library/Caches/im.riot.app.ShipIt/

[Behodar]

Now that you mention it, yes, I think there had been an update prompt earlier in the day. The relevant part of ShipIt_stderr.log is attached.

ShipIt_stderr.log

[Djspaceg]

I'm now experiencing this as well on an Apple M1. Not really sure why. It's a very new laptop, only 2 weeks old.

I received an update prompt from Kaleidoscope.app earlier today, and followed through with the update.

A "soft" terminate of the process allowed it to relaunch with normal (tiny) CPU load.

[ErikThorsell]

I also wonder what this is all about, as I just saw this:

[hvdschmitt]

Had ShipIt running at 100% today on MBP16,1. Running Ventura 13.0 release installed yesterday (external SSD).
"Soft" terminate in activity monitor made the process go away. I'll report back if it re-appears after reboot.

Edit: ShipIt didn't reappear after reboot.

[fuentco]

I have an old Macbook air that I use only searching the web. Inadvertently launched the WhatsApp (that does not have an account associated) app and the fan starter to run like crazy. Then I found the ShipIt process running at 99%. So, it could be a mysterious application related to WhatsApp.

[hvdschmitt]

Just tried with my MBP16,1 under Monterey - started WhatsApp but no signs of ShipIt, also after terminating WhatsApp again. Anyway, different setting. I'll also try with Ventura later.

…

Am 27.10.2022 um 02:15 schrieb Erick Fuentes ***@***.***>: I have an old Macbook air that I use only searching the web. Inadvertently launched the WhatsApp (that does not have an account associated) app and the fan starter to run like crazy. Then I found the ShipIt process running at 99%. So, it could be a mysterious application related to WhatsApp. — Reply to this email directly, view it on GitHub <#647>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATTMYWW2M3I5VAVDGQHCGCLWFHCSRANCNFSM5W3PQ7MQ>. You are receiving this because you commented.

------ Hans von der Schmitt Schwandenhubelstr. 19L CH-3098 Schliern b. Köniz Tel. 0041-31-3056703 ***@***.***

[AndrewJSong]

macos 13，Ventura。My shiplt process was created by bilibili and when I tried to forcibly terminate the process, the Bilibili client opened automatically. Originally the Bilibili client was closed and not running in the background.