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
Comments (362)
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
- Xbox One controller does not work and is not recognized in Unity Editor when plugged in via USB cable
- Scrolling speed is inconsistent in runtime when using UI Toolkit ScrollView
- The particle effect breaks when using "Set Alive" VFX Graph module and a shader with "Tiling And Offset"
- Lens Flare shines trough GameObjects when Screen Space Occlusion is enabled and Graphics API is set to OpenGLES3
- Objects cannot be selected through the Scene view when Mesh Renderer Component is not attached
smithhax
Sep 13, 2019 17:56
I agree with the above solution, we can handle these issues by increasing the hardware working resources Like GPU or CPU capabilities to meet the needs of screen high-resolution requirements. https://procrackerz.org/matlab-crack-full-download/
tyuer
Jul 16, 2019 11:14
Any computer program that needs more CPU power and RAM than a personal computer can probably afford can use these types of servers.https://procrackpc.com/templatetoaster-crack-torrent/