Search Issue Tracker
Fixed in 0.2.7-preview.1
Votes
0
Found in [Package]
0.2.5-preview.1
Issue ID
1275855
Regression
No
[Memory Profiler] Multiline string values do not fit in the table row when looking through Memory Captures
How to reproduce:
1. Create a new Unity project
2. Install the Memory Profiler package
3. Open Memory Profiler window
4. Unzip and import the attached file "case1275855_snapshot.snap"
5. Click "Open" on the attached file in the Memory Profiler window
6. Click on the "System.String" section
7. Observe the top bar of the Memory Profiler window
Expected result: Warning message fits in the Memory Profiler window and is readable
Actual result: Warning message does not fit in the Memory Profiler window and is not readable
Reproducible with: 2018.4.27f1, 2019.4.10f1, 2020.1.5f1, 2020.2.0b2
Reproducible with package versions: 0.1.0-preview.2, 0.2.5-preview.1
Could not test with package versions: 0.1.0-preview.1 (Memory profiler window layout is different)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note (fix version 0.2.7-preview.1):
Issue postponed until we do a bit of cleanup to the table functionality of the Memory Profiler.