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
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- WebGL sends wrong value with large numbers when SendMessage function is used
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
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