Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(91)

Unified Diff: chrome/browser/android/monochrome_entry_point.cc

Issue 2501193003: Selectively perform JNI registration in render processes on Android. (Closed)
Patch Set: Address Ted C comments Created 3 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/browser/android/monochrome_entry_point.cc
diff --git a/chrome/browser/android/monochrome_entry_point.cc b/chrome/browser/android/monochrome_entry_point.cc
index a3c7f30457b627518a80a8f9137ec071ba72bc90..7a04309c33c0487a927be986397158be35dc8ab1 100644
--- a/chrome/browser/android/monochrome_entry_point.cc
+++ b/chrome/browser/android/monochrome_entry_point.cc
@@ -36,8 +36,8 @@ bool NativeInit() {
// This is called by the VM when the shared library is first loaded.
JNI_EXPORT jint JNI_OnLoad(JavaVM* vm, void* reserved) {
- base::android::DisableManualJniRegistration();
base::android::InitVM(vm);
+ base::android::SetJniRegistrationType(base::android::NO_JNI_REGISTRATION);
base::android::SetNativeInitializationHook(NativeInit);
return JNI_VERSION_1_4;
}

Powered by Google App Engine
This is Rietveld 408576698