Search Issue Tracker
Fixed in 1.0.3
Votes
0
Found in [Package]
1.0.2
Issue ID
1266375
Regression
Yes
Profile Analyzer generates compiler warnings on 2018.4
Version 1.0.2 of Profile Analyzer generates a CS0414 warning in Unity 2018.2.24f1 regarding field ProfilerWindowInterface.s_UseRawIterator
How to reproduce:
1. Open any project in 2018.4
2. Open the Package manager and search for the Profile Analyzer
3. If it is already installed, remove it first
4. Clear the Console
5. Installing the Profile Analyzer version 1.0.2
Expected: No compiler warnings related to the package appear in the Console
Actual: 4 compiler warnings appear in the console, one of which is new in 1.0.2 compared to 1.0.1
The warnings are:
#1: com.unity.performance.profile-analyzer@1.0.2/Editor/Histogram.cs(68,19): warning CS0219: The variable `range' is assigned but its value is never used
#2: com.unity.performance.profile-analyzer@1.0.2/Editor/TopMarkers.cs(380,17): warning CS0219: The variable `markers' is assigned but its value is never used
#3: com.unity.performance.profile-analyzer@1.0.2/Editor/ProfileAnalyzerWindow.cs(383,22): warning CS0414: The private field `UnityEditor.Performance.ProfileAnalyzer.ProfileAnalyzerWindow.lastSpace' is assigned but its value is never used
#4: com.unity.performance.profile-analyzer@1.0.2/Editor/ProfileAnalyzerWindow.cs(383,22): warning CS0414: The private field `UnityEditor.Performance.ProfileAnalyzer.ProfileAnalyzerWindow.lastSpace' is assigned but its value is never used
#1 is new since 1.0.0, #2 is new since 0.7.0, #3 is new since 0.7.0, #4 is new since 1.0.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment