Android 11+ Too many receivers, total of 1000, registered for pid

[atrope]

Hi,

I wanted to report an issue we've encountered with the cronet_http package in Flutter. We've successfully implemented file downloads using cronet_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

[atrope]

@brianquinlan do you have any ideia what it could be?

[brianquinlan]

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 CronetClients? Do you close them? Do they share one CronetEngine? Do you make large numbers of concurrent requests (e.g. to download images)? etc?

[brianquinlan]

Here is the failing code: https://chromium.googlesource.com/chromium/src/+/0f71a543910198ee5b4104ea0066494a3fcba309/net/android/java/src/org/chromium/net/ProxyChangeListener.java#231

[atrope]

Hey @brianquinlan,
We've been utilizing a single CronetEngine for each download, operating within separate isolates for every download, without closing any of them previously. I'll address this oversight. Although our system supports a high volume of downloads, we maintain a concurrency limit of three, ensuring that a new CronetEngine is initiated only at the start of a download. Consequently, at any given moment, there should be no more than three CronetEngines active within the app.

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.

[brianquinlan]

Hey @atrope

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.

I'm not sure. The stack trace that you sent showed that the exception occurred while Cronet was registering a BroadCastReceiver for the Proxy.PROXY_CHANGE_ACTION.

My hypothesis is that the unregister code isn't being triggered, which eventually causes over a 1000 BroadcastReceivers to be registered. This may be happening because the CronetEngine is not being closed.

I'm going to look at the cronet_http code and see if I can find any places were it is not free resources when it could.

[brianquinlan]

FYI, I have a feature in the works that will make it easier to close CronetEngine if it is associated with one CronetClient:
#1137

[atrope]

Nice, we are now closing so when this is released we will test

[atrope]

@brianquinlan
Here a minimal to reproduce.
https://github.com/SuaMusica/cronet_http_test

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.
Here it is crashing when it gets to 200~500 downloads.

PS: Just tried your branch and it also crashed

  cronet_http:
    git:
      url: https://github.com/dart-lang/http
      ref: brianquinlan-release_engine
      path: pkgs/cronet_http

E/AndroidRuntime(12507): FATAL EXCEPTION: CronetInit
E/AndroidRuntime(12507): Process: com.example.cronet_test, PID: 12507
E/AndroidRuntime(12507): m.ea: Native stack trace:
E/AndroidRuntime(12507):
E/AndroidRuntime(12507): 	at org.chromium.base.JniAndroid.handleException(:com.google.android.gms.dynamite_cronetdynamite@240515038@24.05.15 (190400-0):10)
E/AndroidRuntime(12507): 	at J.N.M6Dz0nZ5(Native Method)
E/AndroidRuntime(12507): 	at m.io.run(:com.google.android.gms.dynamite_cronetdynamite@240515038@24.05.15 (190400-0):13)
E/AndroidRuntime(12507): 	at android.os.Handler.handleCallback(Handler.java:958)
E/AndroidRuntime(12507): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(12507): 	at android.os.Looper.loopOnce(Looper.java:230)
E/AndroidRuntime(12507): 	at android.os.Looper.loop(Looper.java:319)
E/AndroidRuntime(12507): 	at android.os.HandlerThread.run(HandlerThread.java:67)
E/AndroidRuntime(12507): Caused by: java.lang.IllegalStateException: Too many receivers, total of 1000, registered for pid: 12507, callerPackage: com.example.cronet_test
E/AndroidRuntime(12507): 	at android.os.Parcel.createExceptionOrNull(Parcel.java:3077)
E/AndroidRuntime(12507): 	at android.os.Parcel.createException(Parcel.java:3053)
E/AndroidRuntime(12507): 	at android.os.Parcel.readException(Parcel.java:3036)
E/AndroidRuntime(12507): 	at android.os.Parcel.readException(Parcel.java:2978)
E/AndroidRuntime(12507): 	at android.app.IActivityManager$Stub$Proxy.registerReceiverWithFeature(IActivityManager.java:6137)
E/AndroidRuntime(12507): 	at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1913)
E/AndroidRuntime(12507): 	at android.app.ContextImpl.registerReceiver(ContextImpl.java:1860)
E/AndroidRuntime(12507): 	at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:791)
E/AndroidRuntime(12507): 	at m.dw.c(:com.google.android.gms.dynamite_cronetdynamite@240515038@24.05.15 (190400-0):7)
E/AndroidRuntime(12507): 	at m.dw.a(:com.google.android.gms.dynamite_cronetdynamite@240515038@24.05.15 (190400-0):2)
E/AndroidRuntime(12507): 	at org.chromium.net.ProxyChangeListener.start(:com.google.android.gms.dynamite_cronetdynamite@240515038@24.05.15 (190400-0):56)
E/AndroidRuntime(12507): 	... 7 more
E/AndroidRuntime(12507): Caused by: android.os.RemoteException: Remote stack trace:
E/AndroidRuntime(12507): 	at com.android.server.am.ActivityManagerService.registerReceiverWithFeature(ActivityManagerService.java:16672)
E/AndroidRuntime(12507): 	at android.app.IActivityManager$Stub.onTransact$registerReceiverWithFeature$(IActivityManager.java:11530)
E/AndroidRuntime(12507): 	at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:2928)
E/AndroidRuntime(12507): 	at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3195)
E/AndroidRuntime(12507): 	at android.os.Binder.execTransactInternal(Binder.java:1375)
E/AndroidRuntime(12507):
I/Process (12507): Sending signal. PID: 12507 SIG: 9
Lost connection to device.

Exited.

[brianquinlan]

@atrope

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.

[atrope]

Hello @brianquinlan, by setting closeEngine to true, I was able to download 1500 files. I believe this should resolve the issue.

Thank you!

[brianquinlan]

I'll close this issue, thanks for all the help debugging!