[Crash] Firebase crashes on some Windows machines

[Fellhuhn]

Operating system: Windows
Operating system version: Windows 10 (10.0.19044) 64bit
Firebase version: 9.0.0
Unity version: 2021.3.1f1

What steps will reproduce the problem:

• Starting the game (Hnefatafl on Steam) -> Crash

What is the expected result?

• Don't crash...

What happens instead of that?

• It crashes...

The Unity game has been using Firebase for a while now and with the latest update the plugin got upgraded to 9_0_0. Since then some users can't start the game anymore as it crashes right away. The game uses Auth, Database (on desktop) and Messaging (on mobile). The stacktrace:

0x00007FFA7ED1A569 (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFA7ED1B8CB (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFA7ED17751 (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFA7ED18320 (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFA7ED18F89 (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFA7ED19279 (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFA7ED15AB3 (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFA7ED08B91 (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFA7EB81544 (FirebaseCppApp-9_0_0) uS::Node::getLoop
0x00007FFA7EB6B387 (FirebaseCppApp-9_0_0) uS::Node::getLoop
0x00007FFA7EB4F8AF (FirebaseCppApp-9_0_0) uS::Node::getLoop
0x00007FFA7EB4FFBB (FirebaseCppApp-9_0_0) uS::Node::getLoop
0x00007FFA7EB48C39 (FirebaseCppApp-9_0_0) uS::Node::getLoop
0x00007FFA7EB3E791 (FirebaseCppApp-9_0_0) uS::Node::getLoop
0x00007FFA7EFAC9F4 (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFA7ED0245F (FirebaseCppApp-9_0_0) uWS::HttpSocket<0>::upgrade
0x00007FFAF4691BB2 (ucrtbase) configthreadlocale
0x00007FFAF57C7034 (KERNEL32) BaseThreadInitThunk
0x00007FFAF6EE2651 (ntdll) RtlUserThreadStart

All the app does is using custom auth via our backend (REST API) and then accessing a realtime database (listening to changes). If those users change back to the old versions everything works fine. The new version also works fine for other users. So there is no consistency here.

What could be the cause for this issue? As the old version works fine for those users I assume it is not a networking issue on their side.

[google-oss-bot]

This issue does not seem to follow the issue template. Make sure you provide all the required information.

[paulinon]

Hi @Fellhuhn,

Thanks for reporting this to us. In order to identify what's causing this behavior, could you provide a minimal, reproducible example of your implementation?

[google-oss-bot]

Hey @Fellhuhn. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[chkuang-g]

@Fellhuhn

A couple of questions:

• Which SDK version did you upgrade from?
• When it crashes for certain users, did it crash consistently to those users or is it flaky?

Thank you,
Shawn

[Fellhuhn]

* Which SDK version did you upgrade from?

I updated from firebase_unity_sdk_8.10.1.

* When it crashes for certain users, did it crash consistently to those users or is it flaky?

It always crashes, the game doesn't start at all.

As it seems the users are still running Windows 7, which might be the issue. Sadly they are not willing to help in resolving the problem.

[chkuang-g]

Thank you for the information.

To summarize, @Fellhuhn saw crashes for Windows standalone build related to websocket handshake upgrade on Windows 7 machine after upgrading Unity SDK from 8.10.1 to 9.0.0.

It does not seems to have any change in uWebSocket, the third-party SDK we use.
Both versions were built from https://github.com/firebase/firebase-unity-sdk.

More investigation may need to be done.

[chkuang-g]

There are some change to boringssl from 8.10.1 to 9.0.0. This may be the cause.
firebase/firebase-unity-sdk@v8.10.1...v9.0.0

I'll mark this as a bug for now.