1698174 - GeckoThread.getProcessName is not compatible with isolatedProcess

Status: RESOLVED FIXED

(GeckoView Graveyard :: Sandboxing, enhancement, P1)

Description

[(No longer employed by Mozilla) Aaron Klotz]

This breaks our MOZ_DEBUG_CHILD_WAIT_FOR_JAVA_DEBUGGER environment variable.

Stack:

    java.lang.SecurityException: Isolated process not allowed to call getRunningAppProcesses
        at android.os.Parcel.readException(Parcel.java:1683)
        at android.os.Parcel.readException(Parcel.java:1636)
        at android.app.ActivityManagerProxy.getRunningAppProcesses(ActivityManagerNative.java:3818)
        at android.app.ActivityManager.getRunningAppProcesses(ActivityManager.java:3053)
        at org.mozilla.gecko.GeckoThread.getProcessName(GeckoThread.java:584)
        at org.mozilla.gecko.GeckoThread.maybeWaitForJavaDebugger(GeckoThread.java:498)
        at org.mozilla.gecko.GeckoThread.run(GeckoThread.java:426)

Comment 1

[(No longer employed by Mozilla) Aaron Klotz]

Attachment: Bug 1698174: Remove support for MOZ_DEBUG_*_WAIT_FOR_JAVA_DEBUGGER environment variables; r=#geckoview-reviewers

We observe that, while we don't have proper access to the ActivityManager,
we can figure out the name of our own process just by using details about the
name of our GeckoServiceChildProcess class, plus the app's package name.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/16e354847fa2
Remove support for MOZ_DEBUG_*_WAIT_FOR_JAVA_DEBUGGER environment variables; r=geckoview-reviewers,agi

Comment 3

[Atila Butkovits]

https://hg.mozilla.org/mozilla-central/rev/16e354847fa2

Comment 4

[Chris Peterson [:cpeterson]]

Moving isolated process bugs to the new GeckoView::Sandboxing component.