FUSION keeps crashing/freezing whole system multiple time a day for the past week or so!

[ImDaveM]

I have had my entire MAC os system freeze multiple time when Fusion is running. 

I may have a few other apps running ( nothing intensive) , and even if fusion is in the background doing nothing my whole system will freeze!, No mouse, no force quit, have to power off!

Luckily I have not lost any data as the mac recovery works pretty well!

This has been happening for the past week or so!

I am using..

IMAC 27" 5K, 2017 3.4G Intel i5, 8GB ram 2400mhz, DDR4 Radeon Pro 570 4-GB

MAC OS Mojave 10.14.6 (I still need 32 bit apps, that's why i don't use catalina or Big Sur)

Any ideas!

Dave M

[g-andresen]

Hi,

Can you show for which files or actions this happens?

günther

[tyler.popeG3LPF]

Same issue here. Doesn't matter what file I have open. It locks up and has to be forced closed. If I restart the software without restarting my computer it doesn't have enough memory to function. 

Windows was updated recently if that helps find the problem. 

[Phil.E]

It might help to see log files. These are found on the Help menu, under support and diagnostics.

[ImDaveM]

Fusion can cause my mac to freeze even when i am not using fusion!

It crashed again today!

happening nearly everyday!

I am getting very frustrated with fusion in many ways.

1) Slowness

2) Crashing

3) Electronics is so painful to use! 

how do i send you my Log files?

[Phil.E]

@ImDaveM 

I see your crash reports. Thanks for sending those. Although I only found a handful of reports. So be sure to send every one so the system correctly collects and shows me the right amount of report activity.

Just to be clear, when you say Fusion crashes your machine while you aren't using it, do you mean that you think the Fusion 360 application is not running at the time this happens?

The history of your reports is consistently showing issues we've identified but cannot reproduce in debugging machines. It is related to the internal machine processing speed.

Please try these steps:

1. Restart your computer

2. Start only Fusion 360

3. Open only the one design you wish to work with

4. Use Fusion as needed for some time

Does the problem happen again? If it does, please gather your logs and then attach them here in a response to me. Glad to take a look.

[ImDaveM]

Hi Phil,

I think this problem was due to that fact i have HIGH RES MODE for GRAPHICS turned on.

Fusion 360 was gobbling up a ton of ram! and slowing down my whole system, I only have 8GB, my SSD is super fast  9 over 1500+MBs, but I only have the Intel i5 Processor, I am waiting on the new MAC MINI M1 MAX computers to come out soon!

Seems to be better with graphics set low, ( although it looks like crap!)

[infoEMRZJ]

I'm having the same problem on Windows 10

As far as I can tell there's a serious memory leak as of the last release.  RAM usage balloons over a couple hours of usage until fusion simply closes.  I have had this happen probably 20 times over the last few weeks, and only once has it prompted me to send a crash report.

I'm editing a single file almost every time.

The reason I think it's a memory leak is because windows isn't reporting that Fusion is using that ram, but it's the ONLY thing I have running on this machine.  In fact windows doesn't report at all which process is using that ram.  Total of all processes (not just my user) accounts for about 2 gigs of ram, and 85% of the machine's 16 gigs were "in use" according to windows. When I close fusion normally, the ram isn't released normally, but does slowly get released over the next hour or two, I'm guessing by some windows cleanup process.  rebooting the machine to clear the consumed ram is basically my only option, and restarting every couple hours is getting pretty tiring.

I've attached logs that were collected immediately after the last time this happened.

I'm happy to help however I can to get this resolved, because it's a pretty serious problem on my end.

[ImDaveM]

hmm..

I have one assembly open, its quite large and my system process say its using 5.8GB of ram ( out of my 8gb) and its just idle at the moment

[Phil.E]

Regarding what you describe as a memory leak:

Can you describe your workflow a bit? I'd like to try to replicate the effect but it would help to know what sort of activities you do when modeling. Do you render, CAM, Simulate, make electronics, or anything like that?

[infoEMRZJ]

lately, the majority of my time has been spent in the manufacture tab.

My workflow is pretty simple.  I'm designing a solid part, and generating toolpaths for it for a 3 axis mill.  Haven't been doing any kind of stress analysis or anything.

I do a little bit of simulation in the manufacture tab, but not a lot.

[Phil.E]

Would it be possible to share a design with me? If you can replicate the issue again, and send me the file, it's possible we can use it for debugging.

[infoEMRZJ]

I'll throw something together for you soon. I've been working on 4 different files, and the behavior doesn't seem to be specific to a single file.

[ImDaveM]

yes, it happens on ANY project! not just one in particular.

It happens less often with LOW RES GRAPHICS ,

[Phil.E]

@ImDaveM I don't recognize that setting. Can you describe how to enable it?

[infoEMRZJ]

I don't have a file I can share with you yet, but I've been doing a lot more testing over the last week, and I'm no longer convinced it's a fusion360 problem, I think it's a windows memory allocation bug.
I have some hardware arriving in a week or so, I'm going to do some more testing when it arrives.

[Phil.E]

Thanks, please let me know what you find. 

[infoEMRZJ]

Sorry it took so long to get back about this, but I finally nailed down what was causing the problem I was having.

I have windows 10 running in a VM.  I originally had ballooning memory configured (The hypervisor will allocate memory for the VM as the VM requests it, but from the perspective of the OS in the VM, the maximum configured amount of memory is always available).  It appears that there is a bug in Windows so that it's not reporting memory usage back to the hypervisor correctly.  As a result, the ballooning doesn't happen correctly.  The VM runs out of memory, despite windows thinking it has lots available, which ends up causing all kinds of memory allocation problems.

If anyone has a similar problem, do not use ballooning memory with windows VMs.

I do NOT understand why this wasn't a problem with previous versions of Fusion, and began with the update that prompted this thread.  My only guess is that Fusion changed how it was allocating/cleaning up memory usage.