Announcements
Visit Fusion 360 Feedback Hub, the great way to connect to our Product, UX, and Research teams. See you there!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

senddmp spinning

senddmp spinning

When Fusion 360 crashes (which is incidently still far, far more common than it should be), it launches a process «senddmp» which, itself, often hangs and ends up using a ton of CPU time even after killing the frozen crash reporter.

 

In the last few days alone, I've had a couple dozen crashes where the crash reporter froze before sending the report in or completing the process (no way of confirming one way or another). My MacBook Air's fan has been running constantly which I attributed to Fusion 360 constantly churning (which is another issue) but then I noticed it was still going even though I stopped using the program last night. I looked in Activity Monitor and saw a few instances of «senddmp» running, each using 100% of a hyperthreaded core so I'm guessing it's a single thread caught in some sort of a loop.. all of the above is super annoying and should be fixed before you start charging 🙂

10 Comments
schneik-adsk
Community Manager
Status changed to: オートデスク審査落選
Are you on 10.9?
Anonymous
Not applicable
Yeah.. actually now 10.9.1 13B35 but I had the same issue in the GM of 10.9
Anonymous
Not applicable

I know you accepted this already but just because it keeps happening, it's freezing here

 

Capture d’écran 2013-11-27 à 12.49.14.png

 

then after I kill that I've got this going forever until I force-quit it.

 

Capture d’écran 2013-11-27 à 12.49.45.png

Seychellian
Advocate

Same problem for me. I have senddmp taking up 100% of my processor and I dont even have AutoCAD running. Help!

kennymillar
Enthusiast

I am seeing this too,

currently senddmp is using 59% of my total cpu

kennymillar
Enthusiast

To kill the process without re-booting this is what I did...

 

Open a new terminal session using the terminal app.

enter top -o cpu to find the process ID for senddmp

then issue this command to kill it:

 

sudo kill -9 <processID>

 

For example, on my system it was:

sudo kill -9 2502

 

make sure you use the correct process id.

schneik-adsk
Community Manager
Status changed to: Implemented
 
schneik-adsk
Community Manager
Status changed to: Implemented
 
schneik-adsk
Community Manager
Status changed to: Implemented
 

In the production release ?

 

It's at least still getting stuck (and taking an aggressive kill -9 to actually end it)..

 

Capture d’écran 2014-04-19 à 14.47.44.png

 

Capture d’écran 2014-04-19 à 14.48.47.png

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea  

Autodesk Design & Make Report