Search Issue Tracker
Fixed
Fixed in 6000.0.43f1, 6000.1.0b11, 6000.2.0a7, 7000.0.0a22
Votes
0
Found in
6000.0.39f1
6000.1.0b7
6000.2.0a4
Issue ID
UUM-98014
Regression
Yes
A memory leak happens when an Asset with line topology has a Mesh Renderer Extension Component and the High Quality Line Rendering is enabled
How to reproduce:
1. Open the “LineRendererML.zip“ project
2. Open the “New Scene“ Scene
3. Open the “NewMonoBehaviorScript“ Script in the Project tab
4. Change anything in the script and save the changes to cause a Domain Reload
5. Observe the Console in the Editor
Expected result: Nothing is logged that would involve a memory leak
Actual result: A “Leak Detected“ message is logged
Reproducible in: 2023.3.0a15, 6000.0.39f1, 6000.1.0b7, 6000.2.0a4
Not reproducible in: 2023.3.0a14
Could not reproduce in: 2022.3.58f1 (does not have High Quality Line Renderer Volume override)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- The High Quality Line Rendering has also to be enabled in the Volume overrides
- Reproducible only in HDRP
- This issue regressed at the same time when the UUM-91900 bug regressed, so it’s likely related
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note:
null
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-91900