There’s a problem with severe CPU cycles being used for Resources.UnloadUnusedAssets that manifests itself in the latest 5.3.2p3 patch release that IS NOT in p2.
Attached is a screenshot of the XCODE time profiler showing the stacktrace.
This operation used to take milliseconds… can now sometimes take minutes
I seems met the same problem,
Unloading 5776 unused Assets to reduce memory usage. Loaded Objects now: 5880.
Total: 9257.671875 ms (FindLiveObjects: 3.028875 ms CreateObjectMapping: 2.391375 ms MarkObjects: 9172.416992 ms DeleteObjects: 79.832664 ms)
MarkObjects takes too much time
it still occurs in 5.3.2p4
@skylorder @vqt123 Did either of you submit a bug report for this? I searched but can’t find one.
I’ve been informed this was fixed in 5.3.3f1.
