2017.1.0f1: (Case 924911) Memory Leak when searching in the hierarchy

Searching in the Hierarchy causes Unity to constantly allocate memory up to the point that Unity either crashes or turns unresponsive. Please see video that is attached to the bug-report.

Reproduce

• Open user project
• Open Assets/Scene.unity
• Open Windows Task Manager and select Unity Process
• In Unity, enter "cube" in the Hierarchy search field

Observe in the Windows Task Manager that memory increases (5 GB in a few seconds here).

Expected
Searching the Hierarchy should not cause the editor to crash or turn unresponsive.


PS: I found this item in your issue-tracker:
https://issuetracker.unity3d.com/issues/memory-leak-when-searching-in-the-hierarchy
It says "Not reproduced on: 2017.1.0a2 2017.1.0b5", but now this issue occurs in 2017.1.0f1 as well.

 

These memory leaks are becoming common, is Unity doing anything about them, I seen few reported..

 

I made a thread on it here too:

https://forum.unity3d.com/threads/memory-leak-os-crash-when-filtering-hierarchy-view.476183/

They are tracking it on this bug which says "fixed in future release":
https://issuetracker.unity3d.com/is...view-port-camera-with-hierarchy-search-active

Edit: Actually you posted in that thread. But this does seem like a critical bug for a release candidate.

 

QA identified it as a duplicate:

 

Hm, it is more likely
https://issuetracker.unity3d.com/issues/memory-leak-when-traversing-through-prefab-instances

However, the fix still is in the bug fix branch wending its way towards the release.
I'll look to fast-track it to f2.

 

We actually have testing to make sure we don't introduce more leaks via scripts and standard runtime scenarios - however things like this where it's a specific UI interaction are rather hard to test for this. So, thanks for helping find them and we'll squash them.