Hi @Qleenie ,
I installed 23.2 to see how you could enable ADB in the Search Window.
You need to press the 3Dots button in the search GroupBar:
When it is enabled, you will see AssetDatabase available in the list of searchable Areas:
After you will be able to search using the Adb provider:
oO Is that the same in an empty project or 2022.3?
Hi,
How do you open the Search Window. For this speicifc instance I would advise to open it using the “magnifier icon” in the main toolbar:
I tested in 23.2 and if you open the search window with the menu Window → Seaech → New Window you will get a a different set of search providers (this ius something that has been fixed in u6).
In a nutsheel do not use:
Nice, does that by chance now resolve the issue with the Memory Profiler?
If not and as another test case, you could try copying the Memory Profiler package from the package cache into the Packages folder and changing com.unity.memoryprofiler\Editor\Utilities\EditorAssetFinderUtility.cs by removing SearchProviderIdAssetDatabase from it and seeing if that fixes the issue in opening
crash still happened after doing the search above; however, after removing the SearchProviderIdAssetDatabase from the file you mentioned everything worked!
So what does this mean now?
I’m honestly a bit stumped. Without a repro project, we’ll likely never know for certain. I guess I can make the ADB provider optional via the settings as the asset provider should capture mostly the same items save for some nuances. At least it unblocks you so you can use the latest versions of the package for now 
Could it be that some asset is breaking the adb in some way? I also have one other strange thing, which is a longer hiccup when I scroll through a certain asset folder. That happens every time at the same folder. Just scrolling, no selection.
That coooould be related. If you can isolate it to that folder or even an asset within that, you could try copying that into an empty project (with it’s meta file(s)) and see if it reproduces the crash on opening the profiler, and if so report a bug with that.
And/or temporarily delete it from your project, but only if you can revert that via version control obviously…
I’ll do a binary search by copying parts of the project to a new project and check where it breaks. Hopefully I’ll find out.
The switch to include adb would be good to have, though! Thanks for help so far, at least I am now able to profile memory again.
FYI the 1.1.4 update should solve this for you by no longer defaulting to force starting indexing of the Assets provider on opening the Memory Profiler window. There is an option added to the Memory Profiler preferences to change that behavior further to only rely on the Asset Database (adb) provider, the assets provider, or using both as it used to in case it causes any weirdness.
1.1.4 is not yet released but will go out hopefully soon 
thank you, this is great news!
