Search Issue Tracker
Fixed
Fixed in 1.0.2
Votes
0
Found in [Package]
1.0.0
Issue ID
PROFB-318
Regression
No
Project Auditor - Some UnityEngine methods are reported as Major issue even when the non allocating version of this method is already in use
Taken from the Thread: https://discussions.unity.com/t/introducing-unity-project-auditor-a-tool-to-help-you-optimize-your-unity-projects/1597047/76
Some UnityEngine methods are reported as Major issue even when the non allocating version of this method is already in use (such as GetComponentsInChildren or CalculateFrustumPlanes)
Steps to reproduce:
\\
Actual results:
Expected results:
\\
Reproducible with versions:
Not reproducible with versions:
Can’t test with versions:
\\
Tested on (OS):
\\
Notes:
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
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
- [Linux] Bug Reporter window is in Light mode when the Editor theme is Dark mode
Resolution Note (fix version 1.0.2):
Project Auditor warns about users calling functions which may allocate when you could call a non-allocating version (e.g. GetComponentsInChildren, where you can pass a List in or be returned an array).
In the case where multiple versions with the same name exists, Project Auditor warned anyhow and left it to the user to determine what should be done. With this change we can check to see if the function returns void, and if it does, automatically ignore this call because the List is being passed in.