Search Issue Tracker
Active
Under Consideration for 1.0.X
Votes
0
Found in [Package]
1.0.2
Issue ID
PROFB-402
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment