Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.41f1
2021.3.12f1
2022.1.20f1
2022.2.0b11
2023.1.0a15
2023.2.0a1
Issue ID
UUM-17191
Regression
No
Crash on UI::Canvas::DrawRawMesh when opening the Profiler Window
Reproduction steps:
1. Open the attached project “UnityIssue”
2. Open “Scene” Scene
3. Enter the Play Mode
4. Press “Tap me to crash Unity” button
5. Open Window > Analysis > Profiler
Expected result: Profiler is opened
Actual result: Editor crashes
Reproducible with: 2020.3.41f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0b11, 2023.1.0a15
Reproducible on: Windows 10
Notes:
If the crash doesn’t happen try reentering the Play Mode
Crashes with different stack traces on different streams
First lines of stacktrace:
0x00007ff67a040695 (Unity) UI::Canvas::DrawRawMesh
0x00007ff67a042e54 (Unity) UI::Canvas::RenderOverlays
0x00007ff67a02eb69 (Unity) UI::CanvasManager::RenderOverlays
0x00007ff67a4c7999 (Unity) RepaintController::RenderPlayModeViewCameras
Comments (1)
-
Pop_Slime
Oct 18, 2022 14:29
Reproducible with 2021.3.10f1
NOT reproducible with 2021.3.8f1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.
Resolution Note (2023.2.X):
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.