Search Issue Tracker
Fixed
Fixed in 6000.6.0a1
Won't Fix in 6000.5.X
Votes
0
Found in
6000.4.0f1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-136776
Regression
No
Closure allocation is reported at an incorrect line number when using Project Auditor
How to reproduce:
1. Open the attached “IN-124154_2218818.zip” project
2. Open the Project Auditor (Window → Analysis → Project Auditor)
3. Start Analysis
4. Under the Code tab open “Closure Allocation”
5. Observe the Project Auditor
Expected result: Project Auditor reports a closure allocation in this file on line 18
Actual result: Project Auditor reports a closure allocation in this file on line 0
Reproducible with: 1.0.0-pre.1 (6000.0.62f1), 1.0.2 (6000.0.62f1, 6000.2.12f1, 6000.3.0b10)
Not reproducible with: 0.10.0 (6000.3.0b10)
Could not test with: 1.0.2 (6000.4.0a5, 6000.5.0a1) (Uses a different package, see note)
Reproducible on: Windows 11 Pro (24H2)
Not reproducible on: No other environments tested
Note: Project Auditor is built in on 6.4 but issue does reproduce on 1.0.0 and 1.0.1 of com.unity.project-auditor-rules
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
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have decided this bug is too low priority to be backported to 6.5.
However, we do expect to land a fix in 6.6.
Thanks for reporting it!