1bbb407dc9
* chore: bump chromium in DEPS to 99e60beb593ecf98f8a441e3f03a13b68cfcb311 * update patches * chore: bump chromium in DEPS to b1abadda21f417ba5e8276c4dd779d31445d16cd * update patches * 2146532: gtkui: Fix standalone Ozone/Wayland configuration https://chromium-review.googlesource.com/c/chromium/src/+/2146532 * 2145152: Pass source URL when setting a cookie https://chromium-review.googlesource.com/c/chromium/src/+/2145152 * lint * chore: bump chromium in DEPS to 8897189f1da5a3670bbe32d343767fd71f80d779 * chore: bump chromium in DEPS to 8ac51eeee93a02ed5b81f47e28627079edeecde0 * chore: bump chromium in DEPS to e897b8003f3a5f3c8d654eee9b03c513046ae7ea * chore: bump chromium in DEPS to 7b80f9c82122600291d041c530698616a4716cdf * Update patches * Move definition of WebInputEvent enums into mojo https://chromium-review.googlesource.com/c/chromium/src/+/2152777 * update patches Co-authored-by: Electron Bot <anonymous@electronjs.org> Co-authored-by: Jeremy Apthorp <nornagon@nornagon.net> Co-authored-by: John Kleinschmidt <jkleinsc@github.com>
38 lines
1.8 KiB
Diff
38 lines
1.8 KiB
Diff
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
|
|
From: Cheng Zhao <zcbenz@gmail.com>
|
|
Date: Tue, 4 Jun 2019 11:30:12 +0900
|
|
Subject: crashpad_pid_check.patch
|
|
|
|
When both browser process and renderer process are connecting to the pipe,
|
|
the API may return the PID of browser process as real_pid, which is different
|
|
from the PID of renderer process.
|
|
|
|
This is caused by the crashReporter getting started after the sanbox, after
|
|
we redesign crashReporter's API to make it alwasy start before the
|
|
sanbox, we can remove this patch.
|
|
|
|
See following links for more:
|
|
https://github.com/electron/electron/pull/18483#discussion_r292703588
|
|
https://github.com/electron/electron/pull/18483#issuecomment-501090683
|
|
|
|
diff --git a/third_party/crashpad/crashpad/util/win/exception_handler_server.cc b/third_party/crashpad/crashpad/util/win/exception_handler_server.cc
|
|
index c841f7bc5c3d9962ea24664f26c6867ded529c7b..13218a598bbd4b51cd9a045879ee20b0491f8146 100644
|
|
--- a/third_party/crashpad/crashpad/util/win/exception_handler_server.cc
|
|
+++ b/third_party/crashpad/crashpad/util/win/exception_handler_server.cc
|
|
@@ -445,9 +445,16 @@ bool ExceptionHandlerServer::ServiceClientConnection(
|
|
DWORD real_pid = 0;
|
|
if (get_named_pipe_client_process_id(service_context.pipe(), &real_pid) &&
|
|
message.registration.client_process_id != real_pid) {
|
|
+ // Electron: When both browser process and renderer process are connecting
|
|
+ // to the pipe, the API may return the PID of browser process as real_pid,
|
|
+ // which is different from the PID of renderer process.
|
|
+ //
|
|
+ // I don't understand why Chromium does not have this issue.
|
|
+#if 0
|
|
LOG(ERROR) << "forged client pid, real pid: " << real_pid
|
|
<< ", got: " << message.registration.client_process_id;
|
|
return false;
|
|
+#endif
|
|
}
|
|
}
|
|
|