Search Issue Tracker
Fixed
Fixed in 6000.0.62f1, 6000.2.11f1, 6000.3.0b10, 6000.4.0a5, 6000.5.0a1
Votes
1
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b3
6000.4.0a2
Issue ID
UUM-120152
Regression
No
Crash on UI::Canvas::UpdateEventIndexesRecursive when a script modifies nested Canvases in Play mode while using command line argument -debugallocator
How to reproduce:
1. Open the attached “IN-115489” project with the command line argument “-debugallocator”
2. Open the “SampleScene”
3. Enter Play mode
4. Click the button
5. Observe the crash
Reproducible with: 2023.1.0a12, 6000.0.58f1, 6000.2.0b2, 6000.2.6f1
Not reproducible with: 6000.3.0b3, 6000.4.0a1
Fixed in: 6000.3.0a1
Could not test with: 2023.1.0a11 (Could not solve package errors from downgrading)
Reproduced on: Windows 10 (user reported), Windows 11
Not reproduced on: No other environment tested
Notes:
- Not reproducible in Player
- Sometimes, a pop-up window stating “The memory could not be read” would appear while the Editor crashes
First few lines of the stack trace:
{code:java}
0x00007FF8678C8BC3 (Unity) UI::Canvas::UpdateEventIndexesRecursive
0x00007FF8678C8C53 (Unity) UI::Canvas::UpdateEventIndexesRecursive
0x00007FF8678C7576 (Unity) UI::Canvas::UpdateBatchOrder
0x00007FF8678C7633 (Unity) UI::Canvas::UpdateBatches
0x00007FF8678ACCD0 (Unity) `UI::InitializeCanvasManager'::`2'::UIEventsWillRenderCanvasesRegistrator::Forward
{code}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Add comment