# Better colors in memory map view
**URL:** https://discussions.unity.com/t/better-colors-in-memory-map-view/782962
**Category:** Profiling Tools
**Tags:** Profiling, Feedback
**Created:** [March 29, 2020, 5:32pm UTC](https://discussions.unity.com/t/better-colors-in-memory-map-view/782962 "2020-03-29T17:32:31Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@NuclearC00kie](https://discussions.unity.com/u/NuclearC00kie)
#### Post date: [March 29, 2020, 5:32pm UTC](https://discussions.unity.com/t/better-colors-in-memory-map-view/782962/1 "2020-03-29T17:32:31Z")
I have to use the memory map feature quite often lately.
I find myself really struggling with the colors chosen for this view.
The Yellow and the blue clearly stand out, but the various shades of grean make it very hard understand what is what.
I see
- **black:** from the unity pro skin (I assume this is empty memory, but it’s not in the legend so I’m guessing here.)
- **Very dark green:** Virtual memory
_\*_ **Less dark green:** Native memory (Reserved)
**\* Medium green:** Native memory (Allocated)
Those colors seem the most problematic.
Also please try this with your displays set to a low brightness. The different tints of green get even more unreadable.
Additionally I find it very hard to map a section of memory on the bottom of this view, with a tiny square at the top of the screen.
My eyes start at the section of Memory that I’m interested in, and then have to scan over an array of colors to find the legend.By the time my eyes have found the legend, I forgot the shade of color I was looking for.
Some potential improvements I see:
- Bigger legends
- More distinct colors
- Displaying the type of memory (+ useful information like size of the block), on hover
Let me know what you think.
Kind regards,
Pieter
---
### Author:  [@MartinTilo](https://discussions.unity.com/u/MartinTilo)
#### Post date: [April 6, 2020, 11:08am UTC](https://discussions.unity.com/t/better-colors-in-memory-map-view/782962/2 "2020-04-06T11:08:05Z")
Hi Peter,
Thank you for the detailed feedback. You’re right and the colors chosen here are a bit too close together. I’ll take a look at improving this and the other points you’ve mentioned when I’m going to go over the different views after my current vacation.
Thanks again,
Martin
---
### Author:  [@NuclearC00kie](https://discussions.unity.com/u/NuclearC00kie)
#### Post date: [April 6, 2020, 11:30am UTC](https://discussions.unity.com/t/better-colors-in-memory-map-view/782962/3 "2020-04-06T11:30:23Z")
Thank you for your reply Martin,
Enjoy your vacation!
---
### Author:  [@NuclearC00kie](https://discussions.unity.com/u/NuclearC00kie)
#### Post date: [April 10, 2020, 12:28pm UTC](https://discussions.unity.com/t/better-colors-in-memory-map-view/782962/4 "2020-04-10T12:28:26Z")
Hi @MartinTilo
Here’s some more feedback:
**Tree map:**
Something that I find myself needing a lot of time:
**A total amount of allocated memory in the Tree Map.**
Mockup of expected behaviour:
Having the total amount of memory for each group is interesting, but I’m often also looking for the total amount of allocated memory. I often find myself guessing at it based on the size of the tiles
Also, when you click on a tile in the tree map, you can now see detailed results, but you again lose **the total amount of allocated memory for that tile.**
Mockup of expected behaviour:
Also, there’s no way that I know of, to step back out of the tile details, except for clicking another tile. So once you clicked, you can never see the allocated memory size overview anymore, except by going to the memory map view and back.
**Memory map**
Navigation of the back button is very tricky because its position depends on the name of the object that you have selected.
If you’re looking for references, it can be pretty tedious to go back to the diff view because of this.
Position of back and forward should always be in the same position.
****
Thanks,
Pieter
---
### Author:  [@MartinTilo](https://discussions.unity.com/u/MartinTilo)
#### Post date: [July 29, 2020, 12:11pm UTC](https://discussions.unity.com/t/better-colors-in-memory-map-view/782962/5 "2020-07-29T12:11:31Z")
Hi again,
Just a small update on this:
> [@NuclearC00kie](#):
>
> The Yellow and the blue clearly stand out, but the various shades of grean make it very hard understand what is what.
> I see
>
> - **black:** from the unity pro skin (I assume this is empty memory, but it’s not in the legend so I’m guessing here.)
> - **Very dark green:** Virtual memory
> _\*_ **Less dark green:** Native memory (Reserved)
> **\* Medium green:** Native memory (Allocated)
While we should’ve looked at this earlier, we’ve now discovered that their darkness in 2019.x versions is actually a regression due to Texture2D now assuming non-linear color space by default ☹ . You can track [that issue here](https://issuetracker.unity3d.com/product/unity/issues/guid/1261948/). The main part of the issue is solved but we’re still looking into the other issues that popped up while looking at this.
---
### Author:  [@MartinTilo](https://discussions.unity.com/u/MartinTilo)
#### Post date: [October 1, 2020, 1:11pm UTC](https://discussions.unity.com/t/better-colors-in-memory-map-view/782962/6 "2020-10-01T13:11:40Z")
> [@MartinTilo](#):
>
> we’ve now discovered that their darkness in 2019.x versions is actually a regression due to Texture2D now assuming non-linear color space by default ☹ .
FYI, the fix for the Linear Color Space issue has just landed with the release o [com.unity.memoryprofiler@0.2.6-preview.1](https://discussions.unity.com/t/730398/10) . As noted out on the issue tracker item. We’ll continue to look into further issues with colors and Memory Map though.
> [@](#):
>
> Notes:
> The main issue here seems to be that the colors in the Chart are using non-linear color space while the legend is using linear color space. Linear Color space became the default color space used in new projects during the 2019 cycle, which is why we also treat this as a regression.
>
> 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:
>
> 1. 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
> 2. 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)
> 3. 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.
> For the side aspects noted above, new bug tickets have been raised to track them and their fixes separatedyl
>
> 1. 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/](https://issuetracker.unity3d.com/product/unity/issues/guid/1278205/)
>
> 2. 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/](https://issuetracker.unity3d.com/product/unity/issues/guid/1278203/)
>
> 2 and 3 are tracked as Feature Requests / Necessary Improvements outside of the Issue Tracker.