[Bug] SIGSEGV - Pure virtual function called! #1006
Comments
|
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
shanemccartney
changed the title
paulinon
added
api: storage
type: question
and removed
needs-triage
new
|
Hi @shanemccartney, Could you share the code you're using that references Cloud Storage? If you're able to reproduce the issue, could you also provide a minimal, reproducible example of your implementation so that we can identify what's causing this to happen? |
|
@paulinon, are you sure it's related to Storage? Our assumption (perhaps wrongly) was that the issue was related to Real-time Database. The stack trace mentions Storage. We didn't know much about Firebase's internal operations. Since we didn't use Storage services much in the game/app, it will be much easier to provide you with source code to help identify this issue. Is there a best way for us to provide you with this source code? |
google-oss-bot
added
needs-attention
|
@paulinon Here is some code for now, potentially the issue is that the StorageProgress value is null. This said its strange that this works on some devices and not others. See code with Storage used as is below, if you need to know some of the values of the constants let me know. |
|
Thanks for providing a code snippet, @shanemccartney. At first glance, it doesn't look like there's any apparent issue with the code that might trigger this issue. The firebase-unity-sdk/storage/src/StorageReference.cs Lines 719 to 721 in d8c1957 That said, it could be difficult for us to move this investigation forward without a proper way to reproduce the same behavior. Could you answer a few more questions below, it might give us a clue where to look for:
|
argzdev
added
needs-info
|
@paulinon Thanks, what we have done in the meantime is uploaded a build to Google Play with StorageProgress defined. I will let you know if this resolved the issue for us. To answer your points:
Once again, thanks for your help and I really appreciate it. I will keep you posted on the new build. A simple solution to this problem would be to define StorageProgress, I get how this shouldn’t be needed. It's strange that this issue has been popping up for some users/players since this game has been live for quite some time and only recently have we updated Firebase for other reasons. |
|
Hi @shanemccartney, thanks for the extra details you've provided. We'll try to investigate this further on our side. Let me know if defining the By the way, you've mentioned that the issue popped up after updating Firebase. Could you provide which version were you previously using? Perhaps we can check what changes were done which triggered this issue. |
|
@paulinon If it helps the issue happens in Firebase 11.7.0 through to version 11.9.0. This issue first happened in a version prior to those detailed above. So it’s potentially related to the Android OS. I say this because it appeared suddenly as an issue on a build this had been live for some time. Also the issue only affects a subset of Android users. I will keep you updated, so far nothing logged in crashlytics. However its still only a few days for this build being live in A/B testing. |
google-oss-bot
added
needs-attention
argzdev
added
needs-info
|
@paulinon Unfortunately the same issue happened with defining StorageProgress within the A/B testing. In case this crash log helps it really seems the issue is within how Firebase handles this method for progress listeneing as our implementation of this is as so: Here is the crash log from a user with Android 11 (SDK 30) and a older device the Redmi Note 8 Pro With the message: Doing a quick prompt to Chat GPT to get some insight into the cause for an error related to HandleUsingDestroyedMutex, it seems to be related to one of these things within Firebase and listening for progress. The error "HandleUsingDestroyedMutex" typically occurs when a program tries to access or manipulate a mutex (mutual exclusion) object that has already been destroyed or deallocated. A mutex is a synchronization primitive used to control access to shared resources in multithreaded programming environments. Here are a few common reasons why this error might occur: Double Destruction: If the mutex object is destroyed more than once (i.e., it is deallocated or freed after it has already been destroyed), attempts to access it will result in this error. Access After Destruction: If a thread tries to access the mutex object after it has been destroyed or while it is in the process of being destroyed, this error can occur. Concurrent Access: If multiple threads try to access the mutex object concurrently, and one of them destroys the mutex while others are still using it, this error can happen if proper synchronization mechanisms are not in place. I only provided this in case its helpful, of course I know you most likely know this. Of course its possible that the issue may not be even related to this but this detail could also help hone in and fix this issue more quickly. I only used Chat GPT in this instance as I am not very familiar with these types of errors. |
Description
We have caught the following issue with Firebase 11.9.0
In the Thread message in Google Play there is the message "Pure virtual function called!"
Reproducing the issue
This does not seem to affect all users so far it seems to affect lower end Android devices like the Lenovo TB310FU with Android 13 (SDK 33)
Firebase Unity SDK Version
11.9.0
Unity editor version
2021.3.33f1
Installation Method
.unitypackage
Problematic Firebase Component(s)
Database
Other Firebase Component(s) in use
Analytics, Authentication, Crashlytics, DynamicLinks, Remote Config, Storage
Additional SDKs you are using
No response
Targeted Platform(s)
Android
Unity editor platform
Mac
Scripting Runtime
IL2CPP
Release Distribution Type
Pre-built SDK from https://firebase.google.com/download/unity
Relevant Log Output
If using CocoaPods for Apple platforms, the project's Podfile.lock
Expand
Podfile.locksnippet👀 Replace this line with the contents of your Podfile.lock!The text was updated successfully, but these errors were encountered: