Search Issue Tracker
Fixed in 4.6.X
Votes
0
Found in
4.6.0b17
Issue ID
628845
Regression
Yes
Crash when there is more than a certain number of canvasses in scene and an additional one is enabled (OSX only)
Repro:
1. Open levels/L0A in the attached 'CanvasCrashRepro.zip'.
2. Enable 'Canvas' object in hierarchy, Unity should crash.
3. Reopen the project, disable 'enemyBlockade', enable 'Canvas', enable 'enemyBlockade', no crash.
4. Crash only happens if 16 or more 'largeVirus' objects are enabled. If canvas components are removed, the crash no longer happens.
5. Moving the child objects to root, so that 'healthDisplay' objects are directly in hierarchy has no effect, the crash still happens as long as there already atleast 16 enabled canvasses in the scene when enabling 'Canvas', but not the other way around.
I'm pretty sure that this must somehow be related to 620511, but the crash here is only triggered by enabling the object with canvas and not by it being present in the scene also the stack trace seems to be different.
Not really sure whether this is actually a regression, but it doesn't crash on b7.
Comments (1)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
SpencerS
Jan 30, 2015 16:41
Thank you so much for spelling this out. Had the exact same problem just happen to me. 4.6.0b12