Search Issue Tracker
Fixed in 2018.2.X
Votes
55
Found in
5.3.5f1
Issue ID
810188
Regression
No
Disabling UI crashes at GameObject::IsActive
Steps to reproduce:
1. Open CrashTestDummy.zip project
2. Open SceneA (or SceneB)
3. Click the big button in the middle continuously until the editor crashes.
Reproduced with: 5.3.5p6, 5.4.0b24, 5.5.0a2, 5.6.2f1, 2017.3.0p1, 2018.1.0b2
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
CptDustmite
Jan 05, 2017 08:39
FYI - the source of my crashes was when a script destroyed a Canvas component. It seems that, in certain situations, Unity does not like this.
A similar thread can be seen here, for reference: https://www.reddit.com/r/Unity3D/comments/4xw8fp/unity_54_crashing_when_destroy_is_called/
CptDustmite
Dec 28, 2016 07:22
Different stack trace:
0x000000014126AB60 (Unity) UI::CanvasRenderer::CanvasHierarchyChanged
0x000000014004A592 (Unity) MessageHandler::HandleMessage
0x000000014004AC64 (Unity) GameObject::SendMessageAny
0x00000001403815F2 (Unity) Transform::BroadcastMessageAny
0x0000000141277222 (Unity) UI::Canvas::AddToManager
0x000000014127DAA8 (Unity) UI::Canvas::AwakeFromLoad
0x000000014052DC6A (Unity) AwakeFromLoadQueue::InvokeAwakeFromLoad
0x000000014052DDF6 (Unity) AwakeFromLoadQueue::AwakeFromLoad
0x000000014004BF8D (Unity) GameObject::ActivateAwakeRecursively
0x000000014004C2B5 (Unity) GameObject::SetSelfActive
0x0000000140E8E3C5 (Unity) GameObject_CUSTOM_SetActive
CptDustmite
Dec 28, 2016 07:01
The output stack trace usually ends with the following:
0x000000014004B586 (Unity) GameObject::IsActive
0x0000000141271BE5 (Unity) UI::CanvasManager::AddDirtyRenderer
0x000000014126CE26 (Unity) UI::CanvasRenderer::SetMesh
CptDustmite
Dec 28, 2016 06:53
(Version 5.4.1)
CptDustmite
Dec 28, 2016 06:42
I am also experiencing this crash frequently, at inconsistent places in my game.
The stack traces on crash log differ each time however usually end with GameObject::IsActive, and occur usually when a UI GameObject has been disabled.
Not sure if related, but on older Android devices these crashes seem to be even more frequent.