-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Version 0.60.6 gets "Aw, Snap" in incognito mode with Developer Tools open and you resize the tool window #2799
Comments
I also have this issue if Im not in Private / incognito Mode. |
Reproduced on
|
Pretty easy to reproduce using the original STR, example: Crashes:
Used the following build to reproduce the issue:
|
FrameContentClient of a given frame can obviously be null, lets check it. Fix brave/brave-browser#2799
Updated milestone to 0.59.x; Uplift PRs available here: |
I still have the same on OSX 10.10.5 Any change of size/position of DevTools gets page crashed. "Версия 0.60.13 Chromium: 72.0.3626.53 (Официальная сборка), dev (64 бит)" is free of this. |
Verification passed on
Verification passed on
Verified passed with
|
0.59.25 Chromium: 72.0.3626.53 (Официальная сборка), beta (64 бит) |
When you are in an Incognito window, and open Developer Tools, resizing the Developer Tools panel crashes the page with an "Aw, Snap" message
Steps to Reproduce
Actual result:
The web page crashes to an "Aw, Snap" screen. The Developer Tools Panel display a message: "DevTools was disconnected from the page. Once page is reloaded, DevTools will automatically reconnect"
Expected result:
Web page resizes without a crash.
Reproduces how often:
Easily reproduced in Windows and Linux (Debian).
Brave version (brave://version info)
Version 0.60.6 Chromium: 72.0.3626.28 (Official Build) dev (64-bit) (Windows 10)
Version 0.60.6 Chromium: 72.0.3626.28 (Official Build) dev (64-bit) (Debian Testing)
Reproducible on current release:
My issue is with the Dev Builds
Website problems only:
Additional Information
Google Chrome does not have this problem
The text was updated successfully, but these errors were encountered: