Search Issue Tracker
Duplicate
Votes
0
Found in
2017.3.0b9
Issue ID
970252
Regression
Yes
A crash on (mono-2.0-bdwgc) common_call_trampoline after loading in-game settings
How to reproduce:
1. Open the attached project
2. Open the "GameScene" scene
3. Disable the "GameSettings" game object
4. Enter Play mode
5. press F1 (enables "GameSettings" game object)
6. Repeat 4-5 if Unity doesn't crash instantly
Actual result: Unity crashes.
Reproducible with: 2017.1.2p3, 2017.2.0p1, 2017.3.0b1, 2017.3.0b9, 2018.1.0a5.
Regression introduced in: 2017.2.0p1, 2017.3.0b1.
Not reproducible with: 2017.3.0a7, 2017.2.0f3.
Notes:
If the Game Settings window opens but is empty, most likely after some attempts Unity is going to crash.
I was able to reproduce the crash once on 2017.1.2p3, but the crash is very rare.
Comments (1)
-
mutluadam
Aug 07, 2019 11:12
Thanks!! lolll I solved my issue :)
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
This is a duplicate of issue #967206