Error Reports Storage Location

[Anonymous]

When my Fusion 360 starts up, it comes up with the submit error report and when I submit the error report, it closes.  However, if I move the error report screen to another monitor or maximize the fusion window, I am able to continue to learn the software normally.

I have performed a clean install.

This started when I tried to delete a bunch of items from an imported STL file that had been converted out of mesh to Brep.  The delete failed and the software crashed and wanted to submit an error report.  I normally do not send error reports as a matter of course and canceled out of it.  Ever since, it wants to send an error report and even if I do send one, it does not resolve the problem.  I can assume that it has stored the error report outside of its normal operating area (one not cleaned by the Autodesk clean install program) and keeps on detecting this error report and starting the online submission process that always seems to end with the software being closed.

As a developer myself, I know that if the software had ACTUALLY crashed when I started it up, I would not be able to sideline the error report and work on files using Fusion the way I am doing right now as a workaround the problem.

Since I have the person edition and only qualify for support via the forums, I am asking if anyone in the community has seen this behavior before and knows what I can do to delete the error report (or other data) that is causing this to occur.

Also, I would be interested to know how to turn off the error reporting completely.  In this day and age of privacy concerns and ever-increasing government regulation on companies regarding privacy, this should be an option.

[Phil.E]

Hi,

Thanks for writing. There are a number of things to respond to, so for the sake of brevity and clarity, I'm going to have to tick them off one at a time here.

Moving the crash error report (CER) dialog to another monitor and continuing to use Fusion.

• This is a little strange, but not surprising considering Fusion is actually several processes running together. One of them is crashing on startup, which is why you get the dialog.

"I normally do not send error reports as a matter of course and canceled out of it."

• This is unfortunate because I can't help fix crashes if I don't know you are crashing. The way I find out is by reading the CER reports being sent in. Each error report contains a "call stack" that shows where the program crashed.

Sending in a CER report is not intended to fix the crash somehow. Please don't expect to send in one CER and find that the crash is now fixed. The process for fixing crashes goes like this: Fusion crashes, a report is sent, the CER system registers and sorts the report(s), it's possible to (hopefully) figure out what caused the crash (crash report comments are helpful), a fix is made and tested, and eventually released into production builds that are released during a future update.

The crashes you are seeing are not the result of anything other than Fusion crashing. If Fusion pops up a CER dialog, Fusion crashed.

To avoid any privacy concerns: It's okay to not send in CER reports. Or send them without an email address entered in the box. Also, please take comfort that Autodesk is fully compliant with regulations like GDPR. We take privacy as seriously as possible. 

Thanks for reaching out. I hope this helps. 

[Anonymous]

First, I would like to thank you for reaching out.  I appreciate the time you are taking to do this.  I did send it a couple of CER reports but my main concern is that it somehow is sending in the same report multiple times, hence my request to determine where these are stored.  Is there a way for me to view which Fusion process crashed?   Given your title as software engineer with AutoDesk I trust your analysis of the situation.  It appears however, that the process that is crashing does not seem to affect the usage of Fusion as a program.  I have also removed Fusion, used the cleaner app, and reinstalled it with the issue not being resolved.  After work today, I will create a new user on my PC and install Fusion a second time there as it appears that the install and operation of Fusion is under the users AppData folder and if there is any "bad data" that is causing the crash, and that data is in the AppData folder, this would likely work (as in Fusion would not crash under that user).  I will also run some tools (sysinternals) to log what Fusion is doing on startup and what processes are being spawned and then subsequently crash (or appear to) and if you want those logs, I can provide them.

Fusion worked flawlessly on this hardware for about many days prior to the crash.  So I cannot assume that its hardware based or driver based unless Fusion did an update I was not aware of and the update is taking issue with my hardware or driver versions.  I know my computer did not do an update as I control those on my machine, being a developer myself.  The issue seemed directly tied to a single event in Fusion.  I loaded a complicated STL model (it was convertible to BREP  - it was under over the threshold for a warning, but not over the threshold for the conversion to be cancelled)  On that model I tried to highlight a section of the converted BREP file that was basically all mesh.. probably the most complicated portion of the STL.  The idea was to remove this part of the model.  This operation crashed Fusion and ever since that single crash, it crashes on startup.  I can provide the model for review if need be as I got it from thingiverse.com, I can also describe the part of the model I was trying to highlight if you want to try and re-create the issue.

The reason I point out that I can still use Fusion when the crash window comes up is that even though one of the processes that start with Fusion seems to have died, Fusion itself does not seem to be one of them, but the moment I submit a crash report the crash reporter itself closes Fusion (or appears to).

Anyhow, the problem still exists and any assistance you can provide in solving the reason for the crash would be greatly appreciated.  I have submitted a number of reports at this point so there should be some CER reports with this email address on them.  If you wish me to submit some additional ones, let me know.

[Phil.E]

Hi,

This is confirmed as a crash in a Fusion service, which is why you are seeing the dialog repeatedly. The workaround is to not send the crash report and continue working. We're working on this and should be able to address it soon, but I cannot give any certain answer as to when exactly.

Thanks for your patience,

[Anonymous]

The only method I can find to to not send the crash report is to set the dialog aside.  I do not have a button in the crash reporter itself that says "Do Not Send Report".  Would there be a setting from Fusion that does this? 

Incidentally, I loaded Fusion to see if there was something in the Preferences and it did not crash today.  Odd, it was crashing every single time prior to now.

Anyhow, All I can see in preferences is the "Data Collection and Use" section which does not specifically refer to crashes that I can see and as stated earlier I did not have a "Do Not Send Report" button the crash dialog (which is why I hit the X in the top right corner and when this occurs Fusion closes). 

My only solution at the time was to set aside the crash dialog and continue to work.  Would that be the accepted solution in this case?  Thanks again for your help. 

The magical disappearance of the crash, while welcome, certainly generates its own concerns which need to be investigated.

[Phil.E]

Yes, I meant don't send the report by setting it aside if possible. Thanks for the update, glad it's working for you now.

[Phil.E]

It sounds like you found the workaround we think solves it:

If anyone is facing this: 

• Disconnect your computer from the internet.
• Start Fusion
• Make all documents Read Only
• Shut Fusion
• Connect computer to the internet
• Start Fusion

The bug can be reproduced again if you move editable files using Fusion Team web portal. Until we can release a fix, please avoid moving files using Fusion Team.

Thanks,