brave-browser: Brave crashes when opening the autoplay settings
Description
As mentioned in the title, brave crashes and exits completely when clicking on the autoplay settings under brave://settings/content.
Steps to Reproduce
- Go to settings > privacy and security > site and shield settings > additional permissions.
- Click autoplay.
- Watch brave crash.
Actual result:
Brave shouldn’t crash and show the relevant submenu.
Expected result:
Brave crashes and has to be relaunched.
Reproduces how often:
Easily
Brave version (brave://version info)
Brave 1.29.76 Chromium: 93.0.4577.58 (Official Build) (64-bit)
Revision c4410ece044414ea42fa4ba328d08195e818a99c-refs/branch-heads/4577@{#1076}
OS Linux
Version/Channel Information:
- Can you reproduce this issue with the current release? Yes
- Can you reproduce this issue with the beta channel? No idea
- Can you reproduce this issue with the nightly channel? No idea
Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? Not related
- Does the issue resolve itself when disabling Brave Rewards? Not related
- Is the issue reproducible on the latest version of Chrome? Not reproducible because chrome lacks the autoplay as a setting in there.
Miscellaneous Information:
None.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 3
- Comments: 21 (8 by maintainers)
Confirmed the issue in all
<html> <body>Stable,Beta, andNightly.Crash ID’s:
Stable->dfa36d58-6a5b-4a10-ba0d-f5dc66e79b5bBeta->d9ef3351-8bac-4b9c-95fe-e4d26884edf1Nightly->a53a36d2-ae81-4e3c-b2b1-4528c969d283Thanks a lot @darylsonnier @Tonev , that helped!
Your other Github ticket was also closed on the same day the pull request was merged into
Nightly. Github allows developers to use special words to link an issue to a pull request and close the issue once the pull request is merged, you can take a look over here - https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.Confirmed for:
on 3 different Ubuntu-based machines.
Edit – same issue in today’s update build: