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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
This is a duplicate of issue #967206