Element rendering failures make Brave v1.79.119 unusable


Description of the issue:
Immediately after upgrading the Brave desktop browser to v1.79.119 on macOS (15.5 (24F74) Sequoia), page element rendering failures are making the browser unusable. The issue is persistent and manifests itself in both regular and private tabs. This, for example, is google calendar:

How can this issue be reproduced?
Upgrade to Brave desktop on the latest macOS

Expected result:
Normal rendering of sites and web apps.

Brave Version( check About Brave):
v1.79.119

Additional Information:
Upon request.

1 Like

Can confirm same result on Windows 10 (Build 19045.5917).

How it happens completely depends on the tab I’m using and seems random, sometimes I simply open a completely new tab and it happens, sometimes if I reload a suspended tab it will occur as well, and sometimes it even happens when switching tabs.

Best fix i found, at the very least on my end, is to close the tab and re-open it.

Compare with one or more of Google Chrome, Microsoft Edge, Vivaldi? Each being up to date and using the same version of Chromium used by your copy of Brave Browser.

Latest Chrome (Version 137.0.7151.69 (Official Build) (arm64)) is running fine on the same machine. I had to switch to using it because Brave isn’t rendering any document (or its own UI) well anymore.

Case in point: I wish I could see the full versioning info in Brave, but I get this instead:

@rlcreator

In a Brave Browser New Window:

brave://version

In order to help you get the general idea of that type of URL address (brave://crashes), in another Brave Browser New Window’s URL address field, enter:

  • brave://chrome-urls/#internals

You will see a long list of the brave:// . . . -type URL addresses used by Brave Browser.

notbook upgrade here

@rlcreator @cleanclouds does disabling hardware acceleration resolve? cc @Mattches for tracking as well.

Same issue, even when going to About - it won’t render that properly either. Entire top half is black, have to highlight text to make it show (per screenshot):

EDIT, even more wackiness when trying to check for updates:

same here…
disabling hardware acceleration solved it!!
but now everything is slow…

I have the same issue.
Some logs that might help:

[34956:903161:0618/110414.772262:INFO:third_party/skia/src/gpu/graphite/dawn/DawnGraphicsPipeline.cpp:697] [graphite] ** ERROR ** Failed to create render pipeline (4): Error creating pipeline state Compiler encountered an internal error
 - While initializing [RenderPipeline "RP((BGRA8+D24_S8 x4->1).rgba) + MiddleOutFanRenderStep[EvenOdd] + (empty)"]
    at InitializeImpl (../../third_party/dawn/src/dawn/native/metal/RenderPipelineMTL.mm:470)


[34956:903161:0618/110414.772313:INFO:third_party/skia/src/gpu/graphite/QueueManager.cpp:208] [graphite] ** ERROR ** Adding Recording commands to the CommandBuffer has failed

[34956:903161:0618/110445.365649:INFO:third_party/skia/src/gpu/graphite/dawn/DawnGraphicsPipeline.cpp:697] [graphite] ** ERROR ** Failed to create render pipeline (4): ShaderModuleMTL: failed to get the MTLFunction '' from produced MSL shader below:



Available functions are:
 - While  getting fragment MTLFunction for [RenderPipeline "RP((R8+D16 x1).a000) + CoverBoundsRenderStep[NonAAFill] + SolidColor SrcOver "]
 - While initializing [RenderPipeline "RP((R8+D16 x1).a000) + CoverBoundsRenderStep[NonAAFill] + SolidColor SrcOver "]
    at CreateFunction (../../third_party/dawn/src/dawn/native/metal/ShaderModuleMTL.mm:479)


[34956:903161:0618/110445.365686:INFO:third_party/skia/src/gpu/graphite/QueueManager.cpp:208] [graphite] ** ERROR ** Adding Recording commands to the CommandBuffer has failed

Similar issue as well
Brave 1.79.126 (Official Build) (arm64)

Chromium: 137.0.7151.119

[23180:1910891:0619/115030.327143:INFO:third_party/skia/src/gpu/graphite/dawn/DawnGraphicsPipeline.cpp:697] : [graphite] ** ERROR ** Failed to create render pipeline (4): ShaderModuleMTL: failed to get the MTLFunction '' from produced MSL shader below:

Available functions are:
 - While  getting vertex MTLFunction for [RenderPipeline "RP((BGRA8+D16 x1).rgba) + CoverBoundsRenderStep[NonAAFill] + BlendCompose [ LocalMatrix [ Compose [ HardwareImage(0) ColorSpaceTransformPremul ] ] AlphaOnlyPaintColor SrcIn ] SrcOver "]
 - While initializing [RenderPipeline "RP((BGRA8+D16 x1).rgba) + CoverBoundsRenderStep[NonAAFill] + BlendCompose [ LocalMatrix [ Compose [ HardwareImage(0) ColorSpaceTransformPremul ] ] AlphaOnlyPaintColor SrcIn ] SrcOver "]
    at CreateFunction (../../third_party/dawn/src/dawn/native/metal/ShaderModuleMTL.mm:479)

[23180:1910891:0619/115030.327157:INFO:third_party/skia/src/gpu/graphite/QueueManager.cpp:208] : [graphite] ** ERROR ** Adding Recording commands to the CommandBuffer has failed

Disabling “Use graphics acceleration when available” makes Brave useable again.

@jjcatchpa thanks for the follow up, glad that worked.

How can one disable acceleration if one can’t see the options due to the bad rendering?

MAC OS - Can start start the browser with the flag.

/Applications/Brave\ Browser.app/Contents/MacOS/Brave\ Browser --disable-gpu
1 Like

I ended up having to reset my entire Brave profile

Backed up the current settings folder
tar -czvf /tmp/backup.tar.gz /Users/username/Library/Application\ Support/BraveSoftware/Brave-Browser

Removing the old folder and restarting Brave will result in a new profile being created.

rm -rf /Users/username/Library/Application\ Support/BraveSoftware/Brave-Browser

I then copied the various elements from the backup (folder Default/)
Bookmarks - Your bookmark data
Login Data - Saved passwords (though you might want to re-enter them fresh)
Favicons - Website icons
Top Sites - Frequently visited sites

Dont do it without backing it up

1 Like

I can confirm that in the version I downloaded today (and hopefully future versions) the issue is resolved:

Brave 1.80.115 (Official Build) (arm64)
Chromium: 138.0.7204.97

Because rendering was in such bad shape, I had to send the defunct Brave to Trash to do a fresh install of the newly downloaded Brave. Settings and installed extensions seem to have been preserved.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.