Why does Fusion Take So Long to Exit?

[Anthony_Anz]

Not sure when this started happening but it seems that Fusion just takes a really long time to exit.   If I do not have any model open, and I click the X to close Fusion, the fusion window just sits there white for about 10 seconds before the window finally goes away.  What exactly is it doing in those final seconds?  I have no files open, nothing is actively saving/syncing.   Why doesn't it just quit immediately?   

[dsouzasujay]

Hi @Anthony_Anz ,

Good question, and I agree, it can feel a bit odd when Fusion doesn’t close immediately.

Even if no design is open, Fusion still goes through a short shutdown sequence in the background before exiting. During those few seconds, it may be:

• Finalizing any background cloud sync or cache updates
• Closing active services and local processes (Fusion runs multiple components under the hood)
• Writing logs or telemetry data
• Releasing GPU and system resources cleanly

The white window you’re seeing is essentially the UI closing before those background tasks finish up.

A couple of things to check:

• If the delay is consistently around ~10 seconds, that’s generally within expected behavior
• If it’s getting longer over time, it could be worth checking:
  • Network conditions (cloud sync delays)
  • GPU driver updates
  • Whether Fusion is fully up to date

If you’d like, we can also take a closer look at logs to see if anything specific is slowing down the shutdown on your system.

Let us know if the delay increases or starts impacting usability.

[Anthony_Anz]

Thank you so much for the detailed reply.  I can totally understand it's cleaning stuff up in the background.  From a users perspective though it looks like a UI hang.  Perhaps a status bar displaying shutdown progress?

[dsouzasujay]

Hi @Anthony_Anz 

Can you please your machine diagnostic log files?

• How to collect the Diagnostic Log Files for Fusion

We will investigate the log files to see and understand the launch time.

[Anthony_Anz]

Hi Sujay, attached are my log files.     Hope it helps. 

[dsouzasujay]

Hi @Anthony_Anz ,

Thank you for sharing the log files.

Development team also request to share the "Report Performance Issue" report for more details. 

1. Start Fusion application
2. Start CPR recording
3. Close Fusion
4. Stop CPR recording after Fusion close complete.

Please send report after this. 

[Anthony_Anz]

OK. I submitted my performance issue log.  hope it helps.

[dsouzasujay]

Hi @Anthony_Anz 

Could you please share the Performance Report Number or your email?

[Anthony_Anz]

If I can find the report number I'll add that too.  

Thanks!

@Anthony_Anz - this post is being edited to remove PII.

[dsouzasujay]

Hi @Anthony_Anz ,

Thank you for sharing the email, i will request our team to fetch the report number from the email. 

[Anthony_Anz]

Hey, by the way, posting my email address got me a community violation.  I guess keep that in mind in the future when asking people for info.  🙂 probably better to have just asked me for the reference number.  

[dsouzasujay]

Hi @Anthony_Anz 

Going forward, I will try to collect personal details through direct messages. For now, I have your email address, and we have logged an internal ticket (FUS-243813) to investigate further.

[sanjana.shankar.goli]

@Anthony_Anz Thank you for logging a performance report. Our team has looked into the report but it looks like there was only 2 seconds of recording for Fusion. Can you please send us another performance report with the same steps mentioned by @dsouzasujay  ?

1. Start Fusion application
2. Start CPR recording
3. Close Fusion
4. Stop CPR recording after Fusion close complete.

We would need Fusion to run for at least 10 to 15s in the recording to get enough information to investigate the issue. Thanks again!