Waiting for Job issue

Hi,

On unity 5.3.5 here, and I'm doing longer tests of my game and running into consistent major performance issues after playing for around 15 minutes. However the sequence of events leading up to the perf issue don't seem to follow any pattern. So I'm having a hard time pinpointing the exact issue.

It does seem to occur on one scene in particular, and only when the scene is being loaded async.

Using remote debugging WaitingForJob is where a good chunk of the time is being spent. (I attached a screenshot of the profiler)

I see that 5.4.1 has a fix for a potential deadlock issue in the Graphics section. But I'd really like to know what is causing this before updating.

Has anyone else run into this?

 

I'm having the same issue on 5.5.0f3. When I open and run Scene 1 in editor, frame rate stays consistant and high. Same happens when I open and run Scene 2 in editor. Once I have a script in Scene 1 additively load (synchronously or async) Scene 2, my frame rate starts to decay over time, going from ~2000fps down to ~40fps.

WaitForJob appears in the profiler taking up gobs of time, which increases as long as I let the game run in the editor.

I'm at a loss for what would be causing this.

 

IIRC updating to 5.4.1 fixed the issue for me. Perhaps there's been a regression?