Bug Memory profiler die in unity 2022 3 LTS

Hello you two,
Could you both please, if you have any crash callstack, provide that here, or if not, attach a debugger and while it grows out if control, hit pause and show the callstack of where this growth problem happens?

There is a chance that a fix to that is in the works but I want to double-check that, so that you don't wait in vain and can file bug reports if needed so that we can fix any additional bug sooner?

 

yeah

In your IDE, while attached, you can pause the process and see what it is currently doing.

Hmm. I have a suspicion it could be related to forcing a synchronous search via SearchService and that maybe even triggering indexing of assets... This is use to find assets in the project and it is accidentally get statically initialized on snapshot opening. It was synchronous to stabilize the preview and Search and Find in project functionality but I guess it only reaaally needs to be done synchronously in our test suite. I'll try adjusting it accordingly for the next release.

That detailed breakdown is only available in 2023.1+ versions, that tooltip is mistaken. Thanks for pointing this out. I'm fixing that too now.

 

The only thing the Editor & package version that are taking and opening the snapshot are important for ATM is

• (Editor version) what UI APIs (and therefore UI/UX affordances) are available (e.g. UI Toolkit's Multi-column TreeView, which is used for the tables, is available in 2022.1+, making that the minimum version for the package)
• (package Version) what parts of the data are read and how they are displayed in the editor, including but not limited to:
  • potential bugs, bug fixes and new extra processing steps in how that data is read and processed
  • Capabilities to be able to read data that was added to the reported data in-between package versions, i.e. if 2023.1.0a9/10(?) added data for per page Residency status, then a package version that shipped before that date would just not yet have the capability to read that info in. (Note that package finalization for in this case 2022.3 can happen somewhat in parallel to the next alpha so there's a chance, albeit a small one, that a package version that shipped as part of a previous Unity version would already have that capability but in this case, you actually do need version 1.1.x and data reported from 2023.1.0a10+)

So, in contrast to that, the version of the Editor or Player that you connected the profiler TO defines the data set that will be included. And that usually is not backported, due to risks to the stability of that version.
(Exceptions apply like for 2018.4 we backported data changes, specifically because they were necessary to actually helped stabilize the capture process. #DefinitelyNotALawyer)

So TL;DR: the snapshot's data must be reported to the capturing Editor from an Editor or Player of version 2023.1.0a10+ (maybe alpha 9, can't remember definitively).

 

FYI, one bug the issue on opening that you experienced might have been linked to is PROFB-156. The fix for that has landed in the package and will ship with the next package release. The same applies to the fix to my suspicion of SearchService initialization, and the tool-tip wording.

No ETA yet on when that version will ship. Hopefully soon (TM) but there are other critical bugs that still need fixing as well.

To keep yourselves up to data and in case I forget to ping here on release, you can follow this thread to get notified on new releases of this package (as soon as we manually post to them and as long as we don't forget), or follow the (not Unity Technology affiliated) @Needle_Mirror@twitter.com or @needlemirror@mastodon.gamedev.place bot accounts which monitor Unity's package database and automatically post on every Unity Package release.