BUG: Fusion 360 Crash on Section Analysis view toggle double-click

[Anonymous]

I know the recent update was supposed to address this but it's unresolved, I was still getting crashes trying to refine some thin walls.

Recreating the issue is very easy.

1) create any part/body.

2) create any section view analysis feature. Apply feature.

3) double-click the lightbulb on the analysis feature - CRASH

This is happening in all my parts, old and new. Sometimes double-clicking between the icons or feature name seems to trigger it too.

[Phil.E]

Have you tried "not" double clicking the light bulb?

[Anonymous]

Yo Phil, this isn't helpful. I just spent over an hour investigating this for everyone's benefit and it seems you're suggesting I just ignore it. I'm a bit disappointed to see this from an Autodesk employee. It seems this is at least the 3rd time QA has failed to detect these crash circumstances. User's shouldn't need to be on eggshells about triggering a crash. 

Because I edit the feature to 'scan-through' part thicknesses, I was getting interment crashes to the point I would delete and recreate the feature. I think there maybe other ways to trigger this crash but this is what I found would consistently recreate it. I hope the Fusion team can work it out, I was getting crashes trying to edit the feature regardless of show/hide.

[Phil.E · Accepted solution]

Sorry if you got the wrong impression here. I'm busy and wanted you to know that if you single click on the light bulb, that is sufficient for turning it off and on.

We know about the crash when double clicking the name and have also fixed the crash from double clicking the light bulb. I'm the one who figured it out, and the fix will be released as soon as it's had thorough testing and vetting throughout the entire Fusion ecosystem of development. Soon perhaps, but I cannot promise dates.

Thanks for spending so much time investigating it, but I would hope you can see that by using a single click on the light bulb you can firstly affect the visibility of the object and secondly not crash. Does that work or is single clicking also causing crashes? I didn't get that from your report. 

I also wanted all other users who find this post to understand that double click is entirely unnecessary when clicking a light bulb.

Thanks for your time and efforts, sorry for the confusion.

[Anonymous]

Thanks Phil, I understand now. To back up, I kept intermittently getting crashes in an older file where I was attempting to edit the section analysis feature. This was compounded by working on a form and needing to 'finish form' before the section analysis would update with the new solid. The crash was always on the double click to edit, but I couldn't reliably duplicate the issue. I was double-click in the name/icon area to edit. I only later discovered the visibility toggle issue, and perhaps wrongly assumed that my mouse aim was off when I was trying to edit.

In short I tried to reproduce the editing double-click crash several times but couldn't find the exact conditions and maybe bumped into the visibility toggle by chance. The edit crash does seem worse in my old file versus the new files I was trying to reproduce the issue with. If you'd like to investigate, please let me know how I can send/share the file with you. 

Other than the dbl-click visibility toggle, is there any other conditions to avoid? Specifically when working with forms?

[Phil.E]

The only thing that data might do is slow down Fusion enough that the crash is easier to achieve. The double click was sending inputs when they weren't expected, which crashes. So a heavy file might expose it more readily, but the problem has nothing to do with data. We're pretty confident about the fix at this point, thanks for the offer.

Regarding working with Form, I'm not aware of any easy crashes in that arena at this time. There are always those situations where a giant pattern or symmetry (or selection of such things) might cause a brief "hang" but as long as you give it time instead of force quitting it should resolve itself. Even so, that would require an exceptionally large activity to produce any lag.