Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2
2021.2.9f1
2022.1
2022.2
Issue ID
1410334
Regression
No
Editor crashes with no stack trace when loading a new scene in Awake() function
Reproduction steps:
1. Open users attached project
2. Open /_DreamIsland/_Scenes/Title
3. Enter and Exit the Play Mode twice
Expected result: A new scene is loaded
Actual result: Editor crashes
Reproducible with: 2021.2.17f1, 2022.1.0b13, 2022.2.0a8
Could not test with: 2019.4.37f1, 2020.3.31f1 (could not downgrade the project)
Note: sometimes it might take multiple tries for Editor to crash
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
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Resolution Note:
The crash happens in cri_ware_unity.dll!00007ffe85bc55f0() which seems to be a native plugin made by https://www.criware.com/en/
From my investigation this happens in:
```
private void SceneLoaded(Scene nextScene, LoadSceneMode mode)
{
if (nextScene.name==$"{SceneStateEnum.Title}")
{
bgmManager.PlayAndStopBgm(BgmEnum.TitleBGM, false);
}else if(nextScene.name==$"{SceneStateEnum.Tutorial}")
{
bgmManager.PlayAndStopBgm(BgmEnum.TutorialBGM, true);
}
}
```
because `bgmManager` is null and it calls into native code without any check.
By reading the code I see it adds a `sceneLoaded` callback, but it doesn't remove it.
```
private void Awake()
{
SceneManager.sceneLoaded += SceneLoaded;
}
```
This callback will remain registered and `SceneLoaded` will be called every time a new scene is loaded. Adding
```
private void OnDestroy()
{
SceneManager.sceneLoaded -= SceneLoaded;
}
```
solves the issue, but I think a bug report should be filed to the native plugin maintainers to make sure they handle calls on null pointers