LeakCanary is not compatibled with isolatedProcess
Categories
(Core :: Security: Process Sandboxing, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox66 | --- | affected |
People
(Reporter: gcp, Assigned: bugzilla)
References
(Blocks 1 open bug)
Details
(Whiteboard: [geckoview:m88])
Attachments
(1 obsolete file)
E/GeckoCrashHandler(22493): java.lang.SecurityException: Isolated process not allowed to call getRunningAppProcesses
E/GeckoCrashHandler(22493): at android.os.Parcel.readException(Parcel.java:1546)
E/GeckoCrashHandler(22493): at android.os.Parcel.readException(Parcel.java:1499)
E/GeckoCrashHandler(22493): at android.app.ActivityManagerProxy.getRunningAppProcesses(ActivityManagerNative.java:3121)
E/GeckoCrashHandler(22493): at android.app.ActivityManager.getRunningAppProcesses(ActivityManager.java:2219)
E/GeckoCrashHandler(22493): at com.squareup.leakcanary.internal.LeakCanaryInternals.isInServiceProcess(LeakCanaryInternals.java:117)
E/GeckoCrashHandler(22493): at com.squareup.leakcanary.LeakCanary.isInAnalyzerProcess(LeakCanary.java:164)
E/GeckoCrashHandler(22493): at com.squareup.leakcanary.LeakCanary.install(LeakCanary.java:50)
E/GeckoCrashHandler(22493): at com.squareup.leakcanary.LeakCanary.install(LeakCanary.java:39)
E/GeckoCrashHandler(22493): at org.mozilla.gecko.GeckoApplication.onCreate(GeckoApplication.java:314)
Reporter | ||
Comment 1•5 years ago
|
||
Given that we have no control over what this third party code is doing,
we can't reasonably use it in sandboxed processes.
Reporter | ||
Updated•5 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 2•4 years ago
|
||
Per snorp, we should just remove this one.
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
AFAICT this is long-gone Fennec code. Nothing to do here! \o/
Description
•