-
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
Brave tab crashes on youtube when it's memory footprint reaches 4GB #16136
Comments
Does adding |
I'll test it and report back |
The tab still crashed. Apparently it also occurs on past livestreams as well. |
How does youtube get to 4G in size? What does I would try, turning off GPU acceleration via Could try in a clean Brave beta install, with no extensions also., |
Hardware acceleration is already off. I'll do some more testing. |
Hmm, apparently it has nothing to do with the memory reaching 4GB. I now have no clue what the cause is, just that it happens only on youtube when watching livestreams. I assume lots of comments are still the reason, but I have no clue if that's actually true. |
@EnderShadow Can you update to 1.31.87 and let us know if you're still seeing this issue? |
Yes I will. I'll let you know if it occurs again |
Yeah, I've still had it a few times. Sometimes it's a SIG_KILL signal though |
Description
When watching youtube streams with many chat messages the tab will crash with a SIG_TRAP exception. This happens once the memory footprint for the tab reaches 4GB as seen in brave's task manager. This issue has also been happening for a while.
Steps to Reproduce
Actual result:
The tab crashes usually with a SIG_TRAP exception
Expected result:
The tab does not crash
Reproduces how often:
This easily reproduces.
Brave version (brave://version info)
Brave: 1.24.86 Chromium: 90.0.4430.212 (Official Build) (64-bit)
Revision: e3cd97fc771b893b7fd1879196d1215b622c2bed-refs/branch-heads/4430@{#1429}
OS: Linux
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
This may occur when the tab reaches 4GB usage in general, but I haven't tested that. It's also possible that this is youtube.com/sw.js causing the issue.
The text was updated successfully, but these errors were encountered: