Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2018.2.X
Votes
14
Found in
2017.4.1f1
Issue ID
1025433
Regression
Yes
Fatal Error referring RegisterRuntimeInitializeAndCleanup is thrown after playing a scene multiple times in 2017.4
Steps to reproduce:
1. Open the attached project
2. Switch platform to Windows Store
3. Open the HeadsetAdjustment.unity scene
4. Set Simulate in Editor via Holographic Emulation
5. Play the scene
6. Stop the scene
7. Repeat steps 5 and 6 about 30 times
8. Observe the fatal error
Note:
Against Mixed Reality Device Unity crashes silently
With 2017.2.2p3 throws the assertions
Expected results: Unity should not crash
Actual results: Unity crashes
Reproduced with: 2017.4.1f1
Not reproduced with: 2017.2.2p3, 2018.1.0f1, 2018.2.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
Add comment