Search Issue Tracker
Fixed in 0.4.0 preview-6
Votes
0
Found in [Package]
2019.3.0a8
Issue ID
1168219
Regression
Yes
[Regression] Profile Analyzer throws constant NullReference errors and analyzer modes cannot be changed
How to reproduce:
1. Create a new project
2. Add the Profiler Analyzer window
3. Enter Play Mode
4. Open the Profiler Window
5. Observe the Console
Additionally:
6. Try to change Profile Analyzer modes by clicking on the "Single" / "Compare" buttons
7. Observe that they don't work and the modes aren't switched
Expected result: No nullreference errors are thrown, the user can pull analyzer data and switch analyzer modes
Actual result: Constant nullreference errors are thrown while the profiler window is open, the pull analyzer data button is greyed out and the user can't switch analyzer modes
Reproduced in: 2019.3.0a9, 2019.3.0a8 (With Profiler Analyzer version 0.4.0 preview-5; 0.4.0 preview 3)
Not reproducible in: 2019.3.0a7, 2019.2.0b9, 2019.1.9f1, 2018.4.3f1 (With Profiler Analyzer version 0.4.0 preview-5; 0.4.0 preview 3)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment