[Bug] Unity editor crashes on start
See original GitHub issue[REQUIRED] Please fill in the following fields:
- Unity editor version: 2020.3.9f1
- Firebase Unity SDK version: 7.2.0
- Source you installed the SDK: Unity Package Manager with tgz
- Problematic Firebase Component: Firebase
- Other Firebase Components in use: Auth, Firestore, Crashlytics, Remote Config
- Additional SDKs you are using:
- Platform you are using the Unity editor on: Windows
- Platform you are targeting: Android
- Scripting Runtime: IL2CPP
[REQUIRED] Please describe the issue here:
When starting our project in the Unity editor, the editor crashes. The error log shows
Stack Trace of Crashed Thread 24188:
ERROR: SymGetSymFromAddr64, GetLastError: 'Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.' (Address: 00007FF7141C692A)
0x00007FF7141C692A (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.' (Address: 00007FF713FFFCE7)
0x00007FF713FFFCE7 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.' (Address: 00007FF7175663B2)
0x00007FF7175663B2 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.' (Address: 00007FF71792EE29)
0x00007FF71792EE29 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.' (Address: 00007FF717533F98)
0x00007FF717533F98 (Unity) (function-name not available)
0x00007FF8734B10FF (ntdll) _chkstk
0x00007FF87345B474 (ntdll) RtlRaiseException
0x00007FF8734AFC2E (ntdll) KiUserExceptionDispatcher
0x00007FFFFA5B83F3 (FirebaseCppApp-7_2_0) SWIGRegisterStringCallback_StorageInternal
We could narrow it down to the call
firestoreDB.Collection("l").Document(documentID).Collection("p")
,
where documentID
is null
.
While this should be checked in our code that documentID
isn’t null before trying to access the document, the Firebase SDK should also handle this internally to not completely crash the editor.
We’re not using the Storage SDK.
Steps to reproduce:
Relevant Code:
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Bug - Unity Editor crashes on startup
What happens if you completely disable your internet. Airplane mode, for example. Then try to launch the editor and see if the same...
Read more >Unity editor crashes when opening project, with no error in ...
I found the perfect solution to it, just change the name of the scene you are opening in Unity, then directly start that...
Read more >Unity always crashes on startup. Help please. : r/Unity3D
After opening a project from the hub it tries to open the editor, but all I get is a white screen then the...
Read more >Unity editor crash with openXR on startup
I'm using Oculus SDK inside Unity and whenever I try to run Unity with no headset attached it crashes. I've opened a bug...
Read more >PROBLEM FİX ! 2019.3.0f6 unity editor has stopped working
Unity crashes on startup - PROBLEM FİX ! 2019.3.0f6 unity crash course, unity crash bandicoot, unity crash handler 64, unity crash fix, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve taken a look at Firestore’s section of the Unity SDK and found several places where specifying
null
to methods will cause the Unity Editor to crash. I’m going to work on fixing these since crashing is highly undesirable and I’ll change the methods to instead throwArgumentNullException
.I have no idea why
SWIGRegisterStringCallback_StorageInternal
showed up in the stack trace. That’s very odd. So I’m going to ignore it for now and fix the methods to fail gracefully when given null arguments.Thanks @dconeybe for the fix. This should go out in 8.1.0.