For the past few weeks Brave has been crashing whenever I go to MDN (developer.mozilla.org). This is the only site which causes this behaviour. I have tried disabling all extensions to no effect.
Brave version:
Version 1.68.134 Chromium: 127.0.6533.88 (Official Build) (64-bit)
OS Name Microsoft Windows 11 Home
OS Version 10.0.22621 Build 22621
@r25s please go to brave://crashes and check if anything is listed there. If so, copy and paste the Uploaded Crash Report ID. If you see a Send Now button, click it, then close Brave for 30-90 seconds to allow the crash reports to upload. Reopen Brave, go back to brave://crashes, and copy and paste the Uploaded Crash Report ID. This will help Brave’s team investigate the issue.
Then in the interim, could you do a favor and perhaps check the following:
Does disabling Shields have any impact?
Does it happen in a private window?
Does the issue occur in a new browser profile?
Does it also crash on Brave Beta and/or Brave Nightly?
Assuming still occurring in all of the above, can you check if it also happens in Chrome?
Since i I get the same issue i figured i can also provide details/answer, for me brave crashes on some of devloper.mozzila.orgs pages, (specifically /doc pages like https://developer.mozilla.org/en-US/docs/Web/CSS/::selection)
Crash report ID: 113f0000-15c1-690c-0000-000000000000
@LeonNikolai, to confirm, are you saying it works fine in a private window? If so, this suggests the issue is related to either cookies or an extension.
We can reach this conclusion because private windows start a new session with no cookies and disables extensions by default. To troubleshoot, you can try adding extensions one at a time on the new profile, or disable extensions in your primary profile and gradually enable them again until you find the extension or combination causing the crashes. Or you can start off by first trying to clear cookies to see if that’s the issue rather than starting off with extensions.
It may be interesting to see if @r25s will also have the same results or if your issues are separate.
Thanks for your reply, here is the information you requested: (If all the info isn’t yet in this message, I’m gathering it and will update the message)
Uploaded Crash Report ID: 60e40000-15c1-690c-0000-000000000000
(My previous post was hidden by Akismet, perhaps because I was editing the same post repeatedly. Posting again but there may be a duplicate).
Crash Report ID: 60e40000-15c1-690c-0000-000000000000
The results I got are the same as @LeonNikolai:
Also, like @LeonNikolai, I realize that it doesn’t happen on all MDN pages, but it happens when I browse to documentation pages, (such as https://developer.mozilla.org/en-US/docs/Web/CSS/unset)
@r25s weird, I received a copy of your post but for some reason the spam filter is flagging the reply. Then I saw where you tried to respond again and just as soon as it was starting to load, it vanished. I’ve sent a DM to @Mattches and Steeven from Brave in hopes they can check it and free it up. Not sure what’s triggering it. But at least got what you were saying. Sorry for the complication.
In short, it seems like you are saying the same as Leon which is that it’s not happening in private window. If so, then the same as I mentioned…I’d wager that this issue is with an extension you both are using.
The next step is the convoluted one where have to try disabling/enabling or gradually add on new profile until can figure out which one is the root of the cause.
Either that or it’s just a matter of needing to clear cookies…assuming that somehow is the culprit.
I’ve shared these crash reports with the relevant team members. Not seeing this issue on my end at this time. Have either of you tried clearing cache/site data for MDN? If it’s working in a Private window/New profile (where existing site data is not pulled in) then doing this might resolve the issue for your default profile.
I’m having the same problem. MDN site causes Brave to crash. Periodic crashing has been going on for a couple of weeks now - if I leave the browser open overnight (my computer stays on), I have to re-launch Brave the next day. Now, certain sites, such as MDN are causing it to crash anytime I hit the site. I’ve sent crash reports.
Crash report ID: d5150800-15c1-690c-0000-000000000000
@supershwa can you do as the others above, test on private window? If it works there, then it’s cookies or extensions.
What I’m waiting to hear back from @LeonNikolai and @r25s on would be any updates after in regards to whether they figure out extension(s) causing problems or if just simply clearing cookies resolved.
Unfortunately, I think it’s just going to be down to user end testing to distinguish. Or if all of you would list extensions you’re using, might be able to narrow it down on that to whatever you all have in common.
I am hoping @Mattches is able to follow up on the crash reports later, but instincts tell me it might just be the traditional memory issue that seems to happen when extensions cause crashes. But only he or someone from Brave will be able to say that with any certainty.
@Saoiray I’ve disabled all extensions, cleared my cache and cookies, but the problem persists. However, if I use a new profile, it works fine.
@supershwa, this suggests it likely isn’t a cookie issue. Surprisingly, some extensions have caused problems even when disabled—it’s only after removing them that the issue resolved. You could test this by gradually adding extensions to your new profile and see if the issue reappears.
If it’s not an extension, then the issue might be related to settings. Custom filters for Shields and changes to brave://flags persist across profiles, so we can likely rule those out. However, any other changes from the default settings in your original profile could be the cause.
I know it’s a lot of testing, but this approach typically helps identify the problem. In the meantime, it seems like we haven’t heard back from Mattches or others about the crash reports. And since it’s Friday, we might not get a response from the Brave team until Monday at the earliest.
Have forwarded these crash reports to the team for review.
Right-field guess, but it does seem tied to the profile data. This one showed up over the last 2-3 weeks (I didn’t document it) but I suspect it could be related to a recent update that disagrees with a legacy profile setting or two. Perhaps related to the JS injection by the browser?
It’s possible, though I’m leaning towards it being unlikely. If others reported that it didn’t work in a private window but worked in a new profile, I’d consider it more likely. Since the main difference with a private window is that it starts a session with no cookies and disables extensions, it seems more probable that one of those is causing the issue.
I would also expect issues to arise on other websites, but it seems to be limited to just MDN.
That said, my technical expertise is somewhat limited. Beyond being an avid gamer and taking basic computing courses in high school, I haven’t delved deeply into coding.
My focus here on Brave Community is on trying to replicate issues, guiding basic troubleshooting steps, sharing solutions that have worked in similar cases, and tagging in the professionals from Brave when needed. I try to help with the easier issues so that Support can focus on more complex problems. I considered learning Python or Java to get more involved, but my traumatic brain injury and other medical issues have made that difficult.
As for the issue you’re experiencing, I haven’t been able to replicate it on my Windows 11 Pro with any profile. I’ve tried various settings changes but haven’t encountered the problem.
If you try anything new and make any discoveries, it would be great to know. Otherwise, we’ll wait to hear back from Mattches when he can relay any updates.
Understood. Thank you for your expertise!
Thanks for your response. I have tried clearing the site data for developer.mozilla.org and mozilla.org domain, just in case. Neither of these had any effect. I also cleared all cookies in the browser, also to no effect.
I also tried again with all extensions disabled. Still, no effect.
Thanks for your efforts!
I think our devs know about this issue and have already worked out a fix for it. Waiting on a couple replies to confirm.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
