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

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

Issue 2620303004: Remove JNI onload callback vector construction in favour of direct calls. (Closed)
Patch Set: 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..696c92b6bdc60ecd5ce846cf1c6bfde92ab0f5db 100644
--- a/chrome/browser/android/monochrome_entry_point.cc
+++ b/chrome/browser/android/monochrome_entry_point.cc
@@ -10,10 +10,6 @@
namespace {
-bool Init() {
- return true;
-}
-
bool NativeInit() {
JNIEnv* env = base::android::AttachCurrentThread();
int library_process_type = base::android::GetLibraryProcessType(env);
@@ -24,7 +20,7 @@ bool NativeInit() {
break;
case base::android::PROCESS_BROWSER:
case base::android::PROCESS_CHILD:
- return android::OnJNIOnLoadInit(base::Bind(&Init));
+ return android::OnJNIOnLoadInit();
break;
default:
NOTREACHED();

Powered by Google App Engine
This is Rietveld 408576698