Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
5.6.3p2
Issue ID
992056
Regression
No
[Unity 5.6] Calling instantiate on a non-main thread crashes Editor instead of throwing an exception
Steps to reproduce:
1. Open the attached project
2. Open scene cc#1
3. Enter play mode
Expected result: Error: "INTERNALL_CALL_Internal_InstantiateSingle can only be called from main thread" should be printed out in the console
Actual result: Crash occurs
Reproducible with - 5.6.0b8, 5.6.5f1
Not reproducible with - 2017.1.2p4, 2017.2.1p1, 2017.3.0p2, 2018.1.0p5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment