-
-
Notifications
You must be signed in to change notification settings - Fork 341
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
Lots of OutOfMemory #1852
Comments
I don't fully get your problem, @markuswahl-2. Can you please answer the following questions to clarify this issue:
In |
Hi!
We only see these OutOfMemory-reports from iOS devices. Best regards, |
with-context-information-prior-to-7.11.0-redacted.json
|
without-context-information-using-7.11.0-redacted.json
|
FYI, the Cocoa SDK creates the OOM errors on heuristics. There is no 100% guarantee that your app really crashed. Especially on hybrid platforms such as Flutter and RN, we had issues in the past that we created OOMs by mistake. You are not the first person to be confused by these OOM errors. Can you provide a repro for an OOM event maybe? I don't think that the Cocoa SDK causes the missing APP data. I think that one of the recent changes to the dart SDK causes this: Is the APP data only missing for OOM errors or other events as well? |
I see. Thanks for your feedback. We can see reports in sentry for other events where the APP data section is present. In regards to the APP data section and the field "Start Time": After reading the heuristics section you mentioned, I understand that the OOM is reported the next time the app starts. If so, what does the "Start Time" field in the APP section indicate? Is it the start time of the app for the session that had an OOM or is it the start time of the app that reports the OOM (i e the next time the app starts)? If it is the latter, I understand that we can not infer how long the app had been live when (if) it experienced OOM, from the start time field in the APP section. Right? With repro, you mean if we can reproduce it, right? I am afraid not. |
This could be related to #1877 |
Hey @markuswahl-2, can you try to update to 7.18.0, because #1877 might have fixed the issue. |
Will do, thanks! |
I am afraid we still get those errors even after bumping to 7.18.1 of sentry.cocoa. Also we see a sudden other error (but in android of NoClassDefFoundError: io.sentry.flutter.f) after having bumped to 7.18.1. |
I'm sorry to hear that, @markuswahl-2. Does your app do any background work? Could it be that it runs in the background and then goes into the foreground when the user actively opens it? |
I think that is possible. (That's normal for most apps, no?) |
Yes, that's normal for sure, but I'm just asking because it could be that we don't detect this properly. Do you maybe have |
OK, thanks. It is this one, right? It is no entirely clear to me from the docs what Do I understand it correctly that setting It goes without saying that we are very much still interested in getting reports about true OOM, it is just the possibly false OOM reports that we want to skip. 😃 |
(And to answer your question, no we did not have |
No, if you set
Why do you plan on disabling |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Hi Philipp! I was away from keyboard during the summer. I am back now. Have you had some insight into this? Best regards |
Hello @markuswahl-2 Philipp is in PTO. Sorry but we need to wait for him to came back to look into this. We don't have enough bandwidth right now. |
Hello @philipphofmann |
Hey, @markuswahl-2, sorry, no didn't get to that yet. Try to do it this week. |
Hi @kevinrenskers best regards, |
I am looking into this now. |
Hey, @markuswahl-2, Could it be that some parts of your app use We don't have any other ideas what could cause your OOMs at the moment. Do you by any chance have a way to reproduce it now? |
@philipphofmann I can also see that if I just stop the debugger and open it again, but this is likely an exit(0) example, will try a release mode. |
@markuswahl-2 I could not reproduce it using a release build, can you provide a minimal reproducible example and the steps to reproduce it? |
Hi! I am afraid we do not know how to reproduce it. We see it amongst our users, but we have not experienced it ourselves. No user has complained. This leads us to believe that we should ourselves have been exposed to the problem but that it has not manifested itself to us in a visible way. Or that it is a case of a false negative, i e that it is the heuristic-detection of OOM that falsely reports this as an OOM. And no, we do not order the exit of the app. We don't have a way to reproduce it. But our users reproduce it all the time. We do not see a pattern though... |
I understand that OOM is reported the next time the app starts. Is there a way for us to get some insights from sentry about the previous session, ie the session of the app that the OOM is reporting about? Maybe that way we could start to look for some patterns among the sessions that would have experienced the actual OOM. |
Thanks for the update again, @markuswahl-2.
No, not yet, but we have an issue for that #1759. It has a high priority, but I can't give you an ETA for it. This feature would definitely help to get a better understanding of what's going on for you. We might also tackle MetricKit (#1661) in the following months, giving you OOMs with a stacktrace. |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
@markuswahl-2 With #2347 merged, please try out the next release of the SDK to see if the added breadcrumbs for OOM events help to make sense of them. |
@markuswahl-2 did you get round to test this with a current release? |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Platform
iOS
Installed
CocoaPods
Version
7.11.0
Steps to Reproduce
We do not know. These are the only breadcrumbs from sentry.io:
We are seeing this with sentry.cocoa 7.9.0, 7.10.2 and 7.11.0. One difference we see when we upgraded from 7.9.0 to 7.11.0 is that we no longer get the information about APP Start Time. With 7.9.0 we see that all such OOM events occur in the same second that the app was started. After having upgraded to 7.10.2 or 7.11.0 we no longer get that piece of information.
Expected Result
No crash
Actual Result
Tags
environment
production
event.environment
native
event.origin
ios
handled
no
level
fatal
mechanism
out_of_memory
The text was updated successfully, but these errors were encountered: