-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Desktop] Dev-tools causing crashing with STATUS_ACCESS_VIOLATION #10805
Comments
Was easily able to reproduce with the steps - thanks for the report, @Shadow505 😄 Verified this is not crashing in Chrome- my guess is that it's related to our recent Chromium 84 upgrade I was able to upload the crash and it has report ID# 81160000-5fc1-c604-0000-000000000000
|
This is actually pretty popular crash - it is in top10 for renderer process (and even higher without OOM crashes). Similar instances can be found e.g. like this |
I believe this was fixed with #10951 - which we released yesterday. Diff for the Chromium change: @Shadow505 could you try again? Please let us know! |
Description
I am having the exact same issues that has been reported at https://community.brave.com/t/devtools-crash-any-page/123939 but has not received any response. Apparently the issues still exists.
Steps to Reproduce
Actual result:
All tabs from the same domain (e.g. stackoverflow.com) are crashing with STATUS_ACCESS_VIOLATION after step 6.
Expected result:
Open the dev-tools
Reproduces how often:
Everytime.
Brave version (brave://version info)
Brave: 1.11.97 Chromium: 84.0.4147.89
Revision: 19abfe7bcba9318a0b2a6bc6634a67fc834aa592-refs/branch-heads/4147@{#852}
OS: Windows 10 OS Version 2004 (Build 19041.329)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: