-
Notifications
You must be signed in to change notification settings - Fork 355
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
Android 11+ Too many receivers, total of 1000, registered for pid #1136
Comments
@brianquinlan do you have any ideia what it could be? |
I've done some investigation but didn't find anything obvious. Could you tell me more about how your code is structured? Do you create many |
Hey @brianquinlan, Do you believe that simply terminating the older engines could resolve the issue? I'm struggling to understand how this adjustment could impact the specific concern you raised. |
Hey @atrope
I'm not sure. The stack trace that you sent showed that the exception occurred while Cronet was registering a My hypothesis is that the unregister code isn't being triggered, which eventually causes over a 1000 I'm going to look at the |
FYI, I have a feature in the works that will make it easier to close |
Nice, we are now closing so when this is released we will test |
@brianquinlan Just open the app and click the "Download all" button on the bottom. it will eventually crash with said errors. if it does not crash, just change the for from 1000 to 1200. PS: Just tried your branch and it also crashed
|
Did you modify your code to release the engine i.e. https://github.com/SuaMusica/cronet_http_test/pull/1/files It did not crash for me with the loop running 2000 times. |
Hello @brianquinlan, by setting closeEngine to true, I was able to download 1500 files. I believe this should resolve the issue. Thank you! |
I'll close this issue, thanks for all the help debugging! |
@brianquinlan Now that we fixed this one I can see another error coming from using cronet in isolates. They all Happen in the foreground do you happen to know what could be? I am not able to reproduce. Do I Open a new issue for this one? Thanks!
|
I've just noticed this in Crashlytics.
I have set Stack trace
|
Are you making a large number of Clients? |
Between 4 and 7. |
@techouse Can you produce a minimal reproduction of this issue? |
I can't as I haven't encountered it myself. I just saw one customer having this issue 2x on that device via Crashlytics. Maybe it has to do with the fact that I declare the |
Do you create a new
|
I create it in the Provider, however, I only have like 4 of these Providers alive at any time. I should probably create it statically once and then pass it around, right? |
Yes, that would probably be best. |
Hi,
I wanted to report an issue we've encountered with the
cronet_http
package in Flutter. We've successfully implemented file downloads usingcronet_http
within Isolates, and everything functions as anticipated during testing. However, upon deploying our application to production, we've started experiencing crashes that we're unable to replicate in our development environment.This issue appears to be specific to devices running Android 11 and newer. I've attached the stack trace for reference.
Thank you for your assistance.
suamusica.suamusicaapp_issue_b977b22a18970e5a5cfaacac9f8100f6_crash_session_65D35FC702CE0001166B748B6186F256_DNE_1_v2_stacktrace.txt
The text was updated successfully, but these errors were encountered: