FYI, the fix for the Linear Color Space issue has just landed with the release o com.unity.memoryprofiler@0.2.6-preview.1 . As noted out on the issue tracker item. We’ll continue to look into further issues with colors and Memory Map though.
Notes:
Besides that regression, which is caused by a change in the underlying Unity version somewhere in the 2019.x cycle there are some further aspects to this:
Some Native Allocations and Native Objects displayed in the Memory Map do not fall within a Native Region and therefore get drawn at 40% opacity
Even with correct color space, some colors might be a bit too close together or too close to the underlying editor background color (e.g. Virtual Memory in dark theme)
Memory Map doesn’t use Color Blind color palette when switching the color blind setting on in the Profiler window toolbar.
This bug case and its associated fix only concern the issues resulting from a project using Linear Color Space.
a) Native Objects spanning memory address ranges bigger than those covered by the Native Allocations they originate in are being tracked in Case 1278205 https://issuetracker.unity3d.com/product/unity/issues/guid/1278205/
b) Native Allocations (and the Objects within them) falling outside of Native memory regions, aka “Native Memory (Reserved)” are being tracked as Case 1278203 https://issuetracker.unity3d.com/product/unity/issues/guid/1278203/
2 and 3 are tracked as Feature Requests / Necessary Improvements outside of the Issue Tracker.
1 Like