Geometry parsing issue

[Jpjapers]

Sometimes i get a problematic object in a scene that causes parsing times to skyrocket. When this happens and i see its taking several minutes to parse I click stop. When i click stop it will take several minutes for the render window to respond, the stop button remains highlighted and the whole thing just freezes. Its becoming a real obstacle because it makes troubleshooting scenes a huge struggle. Im not getting any RAM warnings to suggest its an out-of-ram issue. Disabling displacement also has no effect.

Has anyone else had anything similar?

It seems to be railclone causing the problem. Ive tried the FAQ fix of converting it to a mesh but the issue doesnt go away and using embedded proxies for some reason causes half of the objects to not render.
Strangely, the railclone object will render fine on its own as will the scene its going into. But combining them has caused this excessive parsing time issue to surface with times in the tens of minutes sometimes. Its a simple railing.

[maru]

As usual, please archive the scene (if possible) and send it to us: https://support.chaos.com/hc/en-us/requests/new

[Aram Avetisyan]

Hi,

We and iToo have done many fixes to make sure parsing is at optimal speed. There may be edge cases left, so please share the scene so we can check it.
We (Corona) are planning a new parsing related optimization (both single and consecutive rendering, especially for high core counts), soon to be released with a DB. Make sure to try the scene with the upcoming DB as well.