| commit | 0fec93682e50d1b0d6e59b917676f6f57efc469a | [log] [tgz] |
|---|---|---|
| author | Andrew Grieve <agrieve@google.com> | Wed Feb 14 09:45:35 2018 -0500 |
| committer | Richard Coles <torne@google.com> | Tue Mar 06 17:17:43 2018 +0000 |
| tree | 57d34ef5220ad1508faad43f7bef16ebcfde8db1 | |
| parent | e84c506fc3b7cc962fac407f465e46e8a6b969e8 [diff] |
Expose Process.isIsolated() Rather than have a process attempt to perform IO / IPC and check if it fails, it makes much more sense to expose this getter. My specific motivation for exposing this information more directly is to be able to perform process-specific initialization logic in Application.attachBaseContext(): https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/ChromeApplication.java?rcl=ac2e180a1265f88dd4030bb35d69f5d0b2dc488d&l=54 Bug: 73343822 Test: Same code that's used in Chrome via reflection. Change-Id: I1505962679da36ac42401230b204bff7b3376b73