Search Issue Tracker
Duplicate
Votes
0
Found in
6000.3.0b1
Issue ID
UUM-116938
Regression
Yes
Clicking “Selected Sample Track” throws errors and no window opens
Steps to reproduce:
- Create a new Unity project
- Go to Window → Analysis → Profiler
- Switch to Edit Mode profiling and record for a few seconds
- Stop recording and select any frame
- In Timeline, select any active Thread (e.g Gfx.WaitForGfxCommandsFromMainThread)
- Click Show → Selected Sample Track
\\
Actual results: The following errors appear:
{code:java}
GUI Window tried to begin rendering while something else had not finished rendering! Either you have a recursive OnGUI rendering, or the previous OnGUI did not clean up properly.
MissingReferenceException: The object of type 'UnityEditor.ContainerWindow' has been destroyed but you are still trying to access it.
Your script should either check if it is null or you should not destroy the object.
{code}
Expected results: Selected Sample Track window should open normally without exceptions
\\
Reproducible with versions: 6000.3.0a2, 6000.3.0b1
Not reproducible with versions: 6000.0.56f1, 6000.1.16f1, 6000.2.2f1, 6000.3.0a1
\\
Tested on (OS): Ubuntu 22.04
-
Resolution Note:
Although the specific error messages are different, this issue is caused by the same root issue.
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-114635
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #UUM-114635