Interactive rendering starts fast but after stop it takes 1-2 minutes.

[OccultMonk]

Interactive rendering start normally (fast), Renders fast, but when I press on stop it locks 3dsmax for more than a minute. Normal rendering does not have this problem, it starts and stops fast. Corona 1.7 Hotfix 4.

[maru]

We have a similar support ticket right now. Is it yours by any chance?
Also, are you using a Xeon or double Xeons?

[OccultMonk]

No, that's not my ticket. I just discovered it today on my just build render computer (AMD Rizen). Still, have to test it on my main computer (older Intel 8 core 16 thread).

[maru]

Thanks for the reply and hold on, we will return to you shortly....

[twcg]

Hey! My dual Xeon at work has the same problem from time to time :) I'll try to make a minidump the next time this happens...

2x Xeon E5-2630 v3

[maru]

Yes, if the freeze takes more than 1 minute it should be enough to generate a minidump.
Here is how to do it: https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006
And then you can post it here, upload here (https://corona-renderer.com/upload), or even start a new support ticket and post it there.

[OccultMonk]

I tested it on my older Intel 8 core, and it works fine there. Not on my new Ryzen 16 Core/32. Could it be caused by using mapped network drive? I use the same drive letter but on the Ryzen it's a mapped network drive.

[OccultMonk]

I tested it on the Ryzen 16 core again today and now it seems to work (same .max file). A few days ago, whatever I tried it froze for nearly 2 minutes after interactive rendering. So I guess there is some bug, but it is not very consistent. No changes made to 3dsmax 2018 or corona installations.

[maru]

That's the problem - the info we are getting is very vague. :(

Please send us minidumps if you are able to collect them.

[OccultMonk]

It started having the 1 to 2minute lag again, using same 3dsmax process (did not restart 3dsmax).

[maru]

We've had a similar case over support recently and the solution was to exclude 3dsmax.exe (and related processes if you are using those, such as backburner, drserver) from Windows Firewall. Adding rules to allow 3dsmax through inbound and outbound connections may help as well: https://docs.microsoft.com/en-us/windows/security/identity-protection/windows-firewall/create-an-inbound-port-rule
You can check if that's the case by simply temporarily disabling the firewall completely.
If you are using some 3rd party antivirus/firewall software, you should also check if disabling it completely fixes the issue. If so, you will probably need to add the relevant processes to exclusion lists.

[OccultMonk]

But that does not make much sense since it works more than 75% of the time. So it must be a bug. There should not be an interaction between ending an interactive rendering and using a firewall. Also, ending a 'normal render' never gives this problem.

[maru]

But still it would be good if you (and anyone with the same issue) could try disabling the firewall, just to see if it's related.
Then it may give us some hint how this could be fixed.

[OccultMonk]

In understand, I will try it.

[OccultMonk]

Is there any update on what is causing this?

[maru]

But still it would be good if you (and anyone with the same issue) could try disabling the firewall, just to see if it's related.
Then it may give us some hint how this could be fixed.

In understand, I will try it.

Is there any update on what is causing this?

It depends. Have you tried with the antivirus? :)

[sprayer]

this is funny)

the problem only you have, and only you can fix it according suggesting of support, or you can send your PC with scene to maru =)

[OccultMonk]

I already disabled the firewall, and it still has the same behavior. Sometimes no problem, sometimes it freezes for 2-3 minutes.

[maru]

I already disabled the firewall, and it still has the same behavior. Sometimes no problem, sometimes it freezes for 2-3 minutes.

Have you completely disabled all firewall and antivirus software?

[maru]

Any updates here? So far, disabling Windows Defender and/or Windows Firewall completely solved the issue in all cases.