render submit needs a timeout when it gets stuck

[charliex2]

i had a few renders que'd up on local render and the last one  was stuck in submitting the render.

the submit icon was updating and i could flick between renders that had happened  and so on but couldnt cancel the render dialog and its modal.

i tried quitting fusion which said it'd save and upload my work but then just got stuck on the render screen with no dialogs and had to force close it

so adding  a timeout on render submit and a way to cancel , or make it not modal please! 🙂

windows x64

[Phil.E]

The render dialog is not modal. It would appear you suffered some kind of crash.

To be clear, are you talking about local or cloud render? Can you repeat it with any specific steps? I'm glad to test it and log a bug report, but I need to repeat the problem.

[charliex2]

as i said local render during submit. the submission icon just kept going and effectively made it modal as it blocked other things from happening.

can't reproduce it on demand, i was putting local renders in to the que and eventually it just got stuck in submitting (at  which point it became effectively modal and no way to cancel it, which is the bit i'm asking for to be added or a timeout)

[Phil.E]

Sure, but a timeout does nothing if it's crashed.

[charliex2]

as i said fusion was still able to bring up popups to ask me to save the file , when i tried to exit so it seems like it was along more along the lines of a thread getting stuck or just waiting for something to happen which wasn't happening so if there was a timeout or way to cancel the submission perhaps it was recoverable vs a hard crash?

[Phil.E]

Perhaps. Let me know if you experience it again with the workflow of adding local renders repeatedly. If it's repeatable for any user, with specific steps, I can log a ticket. Otherwise, it's data dependent, and hardware dependent, and starts to get harder to both provide a solution as well as test a solution.

[charliex2]

yeah totally understood , just really wondering about if there's a way to add the cancel to it, since normally it happens really quickly. i've hammered on it a few times trying to to recreate it but it did happen after a lot of step import/extrusion and so on.

[Phil.E]

Might be a memory issue. Those workflows can increase RAM unexpectedly. 

[charliex2]

hope not, 256GB sysram and a 48GB GPU heh. trying to cut extrude step files always ends up being really cpu heavy and definitely slows fusion down, often wondered about having a property you can set that ignores a body/import rather than having to turn it on and off during work, but thats for another day 🙂