We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
High CPU usage and instability after visiting GitHub gists website and opening a gist page.
I'm not sure if this is a more general bug or just specifically for GitHub gists.
May be related to: https://community.brave.com/t/crash-while-navigating-to-search-results/34151/20
After Bug:
After Closing App off (X): (Service still maintains high CPU usage)
No massive CPU usage for viewing one page.
Easily reproduced
1.47.171 Chromium: 109.0.5414.87 (Official Build) (64-bit) 2dc18eb511c56e012081b4abc9e38c81c885f7d4-refs/branch-heads/5414@{#1241} Windows 11 Version 22H2 (Build 22621.1105)
The text was updated successfully, but these errors were encountered:
This also happens for me... very weird
Sorry, something went wrong.
No branches or pull requests
Description
High CPU usage and instability after visiting GitHub gists website and opening a gist page.
I'm not sure if this is a more general bug or just specifically for GitHub gists.
May be related to: https://community.brave.com/t/crash-while-navigating-to-search-results/34151/20
Steps to Reproduce
Actual result:
After Bug:
After Closing App off (X):
(Service still maintains high CPU usage)
Expected result:
No massive CPU usage for viewing one page.
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
1.47.171 Chromium: 109.0.5414.87 (Official Build) (64-bit)
2dc18eb511c56e012081b4abc9e38c81c885f7d4-refs/branch-heads/5414@{#1241}
Windows 11 Version 22H2 (Build 22621.1105)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: