New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firestore crash - NSInternalInconsistencyException "Cannot allocate memory" #7260
Comments
Hey @jwilsoncredera, thanks for filing this bug. Here's my thought process:
Please let me know if I've missed anything. |
Thank you for the quick response! We'll look into reducing the app's memory footprint. I'll respond once we have more data so we can close the ticket if that resolves the issue. |
One thing to note is that we open Firestore's underlying LevelDB essentially on the first operation we perform. If we're failing this way there has to be some external cause. |
Do you know what the license is for the Gist snippet for total app memory footprints? Since the Gist doesn't mention a license but is a repository, it seems like it can only be used on GitHub projects if I'm interpreting the GitHub Terms of Service correctly. |
Unfortunately, that's an area we specifically cannot help you with. To give you a definitive answer is equivalent to giving legal advice, which we're not in a position to do. My best advice is to contact the author and ask them to explicitly license their work, either personally to you, or by amending the gist to include an explicit license. |
@jwilsoncredera is this still an issue? |
Hi, we did confirm the crash was correlated with high memory usage after using the application for several days in a row without restarting it. To verify this, we set up metrics to log memory usage over time using a correlation ID unique to each application load. I'll close the issue now that we know the root cause was likely related to application memory leaks, giving us the right direction to address it. Thank you for the pointer! |
[REQUIRED] Step 1: Describe your environment
CocoaPods
Crashlytics Device Information:
[REQUIRED] Step 2: Describe the problem
Crashlytics is reporting the following
Cannot allocate memory
crash on a regular basis. A root cause hasn't been found yet, and it hasn't been reproducible in local development environments.Sample stack trace:
Steps to reproduce:
It hasn't been reproducible locally.
Relevant Code:
N/A
The text was updated successfully, but these errors were encountered: