-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chrome: Higher rate of "connection retry failed" renderer process crashes #3664
Comments
The vast majority of crashes are:
A small minority are:
|
Introduce different call stacks for different types of disconnects, and log additional state information in the FATAL message.
It looks like disconnects can occur after browser process shutdown or crash. For example (at M123):
Repeating the above using a Debug build under system load (for example, while building Chromium) may delay execution sufficiently for the retry to trigger. Also, potentially if the render process is left behind as a zombie (see #3614). |
Introduce different call stacks for different types of disconnects, and log additional state information in the FATAL message.
Introduce different call stacks for different types of disconnects, and log additional state information in the FATAL message.
Related chromium-dev question about detecting browser process termination from the renderer: https://groups.google.com/a/chromium.org/g/chromium-dev/c/tFJCeTzvsnc/m/lzYhPAfkAAAJ |
Split the Alloy runtime into bootstrap and style components. Support creation of Alloy style browsers and windows with the Chrome runtime. Chrome runtime (`--enable-chrome-runtime`) + Alloy style (`--use-alloy-style`) supports Views (`--use-views`), native parent (`--use-native`) and windowless rendering (`--off-screen-rendering-enabled`). Print preview is supported in all cases except with windowless rendering on all platforms and native parent on MacOS. It is disabled by default with Alloy style for legacy compatibility. Where supported it can be enabled or disabled globally using `--[enable|disable]-print-preview` or configured on a per-RequestContext basis using the `printing.print_preview_disabled` preference. It also behaves as expected when triggered via the PDF viewer print button. Chrome runtime + Alloy style behavior differs from Alloy runtime in the following significant ways: - Supports Chrome error pages by default. - DevTools popups are Chrome style only (cannot be windowless). - The Alloy extension API will not supported. Chrome runtime + Alloy style passes all expected Alloy ceftests except the following: - `DisplayTest.AutoResize` (Alloy extension API not supported) - `DownloadTest.*` (Download API not yet supported) - `ExtensionTest.*` (Alloy extension API not supported) This change also adds Chrome runtime support for CefContextMenuHandler::RunContextMenu (see #3293). This change also explicitly blocks (and doesn't retry) FrameAttached requests from PDF viewer and print preview excluded frames (see #3664). Known issues specific to Chrome runtime + Alloy style: - DevTools popup with windowless rendering doesn't load successfully. Use windowed rendering or remote debugging as a workaround. - Chrome style Window with Alloy style BrowserView (`--use-alloy-style --use-chrome-style-window`) does not show Chrome theme changes. To test: - Run `ceftests --enable-chrome-runtime --use-alloy-style [--use-chrome-style-window] [--use-views|--use-native] --gtest_filter=...` - Run `cefclient --enable-chrome-runtime --use-alloy-style [--use-chrome-style-window] [--use-views|--use-native|--off-screen-rendering-enabled]` - Run `cefsimple --enable-chrome-runtime --use-alloy-style [--use-views]`
Describe the bug
Chrome runtime is seeing a higher rate of "connection retry failed" renderer process crashes (code here) compared to Alloy (same web content). We should revisit the discussion in #3260 and either (a) increase the timeouts for Chrome runtime, or (b) change the FATAL to ERROR to avoid crashing. Highlights from the previous discussion:
The text was updated successfully, but these errors were encountered: