Update to preview 23 And now starting empty scene is about 15 sec and 6 GB of memory

As title says Unity just got crazy, do anyone knows who is Inspector.Tick and why it allocates so many on start?

 

@Jes28, Inspector.Tick contains things like redrawing editors for MonoBehaviours. So it looks like you've got something selected who's inspector is causing Unity to allocate an enormous amount of memory.

It could be a [CustomEditor] that's doing something broken, or it could be something with custom serialization code doing something broken - an inspected MonoBehaviour has it's serializer run every editor frame (Inspector.Tick) - that includes ISerializationCallbackReceiver stuff. Pretty sure it also goes for ScriptableObjects.

Turn the deep profiler on on something that's allocating 1.4 GB and spending 14 seconds every inspector frame? Brave.

 

Also it can be hight mouse refresh rate which cause editor revresh very offen (even on simple inspector) other guy has same problem before on this forum (his mouse update was 1000 times per second)

 

Thanks

My Test:
- update to latest Unity 2018.3.2f1
- load default layout
- close all windows
- open empty scene
- close Unity and reopen
- press play
- have the same bug considering that Game window is the only opened window
bug itself happend around 5th frame of play

I dont change mouse last year and bug start to happen recently

Enabling Deep Profile cause to eat all 16GB of memory and hard crash, so I need to reload computer to continue working.

Enabling allocation call stacks eat a lot more memory but somehow editor survived, but there is no call stacks for those allocations.

Any suggestions before I will retry on 32GB RAM machine?

 

attach the debugger, break at random points during the freeze and see if you catch something?

if it was your code, i'd say spam Debug.Log (or breakpoints) everywhere...

EDIT: you can set conditional breakpoints on # of hits

 

Thanks a lot.
32 GB Ram was enough to do Deep Profile

And random breaks helps too.

It seems this is ProBuilder fault
Where send all this for repair?

 

I think just following this document should be fine.
https://unity3d.com/unity/qa/bug-reporting

 

(Case 1118897) If it need to someone