Fusion 360 freezes

[peter.jansson]

With the latest update of Fusion 360 the app freezes for a second every so often.

Sometimes just a couple of seconds apart, sometimes longer.

This is the versions of Fusion and MacOS I use:

2.0.12670
macOS 12.3.1 x86_64 (21E258) on MacBookPro18,2

In the activity monitor I can see that it is sandboxd that is briefly using excessive CPU when Fusion freezes/stutters.

I didn't notice this behaviour when using Fusion a couple of days ago.

I'm pretty sure Fusion is updated since.

Regards,

Peter

[Phil.E]

Hi,

Thanks for reporting this. I'd like to know more.

• Does it happen after a fresh restart of your computer?
• Does it happen when doing a modeling operation, such as finishing a sketch, or finishing a feature edit in a big design?
• Does it happen in brand new, empty or nearly empty design files?

Thanks,

[peter.jansson]

Hi,

Yes, freshly restarted computer.

Very simple model, and just rotating it for a bit.

Then after some seemingly random time, sandboxd goes to 100% CPU utilization for a second and everything freezes.

I am using a 3Dconnexion Spacemouse Enterprise if that could be a clue.

/Peter

[Phil.E]

sandboxd is a macOS system service. I'm not sure why it would be involved here. One thing you could eliminate is the spacemouse.

Have you tried running Fusion 360 while the spacemouse is not connected and the 3Dconnexiuon drivers are stopped?

Are you on the latest spacemouse drivers?

[peter.jansson]

Tried without the spacemouse, and still occasional stutters with sandboxd taking a lot of CPU for a second or so.

A quick googling of sandboxd and I found this:
https://www.howtogeek.com/344211/what-is-sandboxd-and-why-is-it-running-on-my-mac/

It doesn't explain what it does for Fusion 360 specifically, but I can imagine Fusion running in such a sandbox and therefore be dependent on sandboxd to allow it access to certain OS or hardware functions.

I really don't have to do anything in Fusion, just have it open and active to see sandboxd go to 80-100% CPU usage for a second or so a couple of times a minute.

I killed the sandboxd process to easier se the change in "CPU time" used by the process.

The process is automatically restarted after a few seconds.

With Fusion closed it hardly uses any CPU at all.

With Fusion running the CPU time counter rises for every "stutter".

As I said in the beginning, I didn't notice this behaviour a few days prior, and I'm pretty sure Fusion was updated just before this starting.

/Peter

[Phil.E]

On two macs, without 3Dconnexion drivers installed, Fusion is running with no sandboxd service running.

• The moment I install the latest 3Dconnexion drivers, sandboxd shows up in the activity monitor.
• Running Fusion after that does not trigger the effect you see.

My guess at this time is perhaps your 3Dconnexion drivers are out of date. You can update them here.

Please let me know if that helps. You could also check the date on your current 3Dconnexion drivers. 

And another test you could do is first uninstall the current 3Dconnexion drivers, see if sandboxd goes away and Fusion runs normally. Then install the latest drivers and see if it goes back to the state you describe here.