Chromium 3D render problem after the huge update

ARM Technical Assistance
,
1

There was a huge update package today which updated 176 different packages. It included a new Chromium. Everything 3d rendered in Chromium is flickering like crazy now.

3

Hi @Sam_Fisher

Your post has been moved to the topic you already created. Please try to keep your topics contained.

I have taken the liberty of adding the chromium tag to benefit topic discovery through forum Search.

Regards.

4

Itā€™s a mesa regression 24.2.7 to 24.3. firefox too have problem with 3d rendering (earth google) and website with transparency layer like X. But no one has made a bug report, no time to do that.

5

A link to any related information might be a welcome addition; Iā€™m sure the OP will appreciate it.

6

No link because no bug report. Simply reverse packages. If others confirm then bug is confirmed .Darsky has confirmed.

env MESA_DEBUG=1 MOZ_LOG="PlatformDecoderModule:5,Layers:5,WebGL:5" firefox

go to earth google

GetShaderInfoLog() ->
0:2(12): error: extension `GL_EXT_shader_texture_lod' unsupported in fragment shader

GetShaderSource() ->

#extension GL_EXT_shader_texture_lod: require
void main() {}

GetShaderInfoLog() ->
0:2(12): error: extension `GL_EXT_shader_texture_lod' unsupported in fragment shader

GetShaderSource() ->

#extension GL_EXT_shader_texture_lod: require
void main() {}

Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize GL_RENDERER "V3D 7.1.7.0" (t=29.3142) [GFX1-]: Couldn't sanitize GL_RENDERER "V3D 7.1.7.0"
GetShaderInfoLog() ->
0:2(12): error: extension `GL_EXT_shader_texture_lod' unsupported in fragment shader

GetShaderSource() ->

#extension GL_EXT_shader_texture_lod: require
void main() {}

Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize GL_RENDERER "V3D 7.1.7.0" (t=29.3142) |[C1][GFX1-]: Couldn't sanitize GL_RENDERER "V3D 7.1.7.0" (t=29.3422) [GFX1-]: Couldn't sanitize GL_RENDERER "V3D 7.1.7.0"
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize GL_RENDERER "V3D 7.1.7.0" (t=29.3142) |[C1][GFX1-]: Couldn't sanitize GL_RENDERER "V3D 7.1.7.0" (t=29.3422) |[C2][GFX1-]: Couldn't sanitize GL_RENDERER "V3D 7.1.7.0" (t=30.5301) [GFX1-]: Couldn't sanitize GL_RENDERER "V3D 7.1.7.0"

That all i knows

1 Like
7

OK, I see it will be easier to ping @Darksky directly for any related information. Cheers.

8

Thanks for the info. I will try to revert mesa package to its previous version and see if it will fix things for me. The issue is our sole ā€œpackage archiveā€ which is ā€œhttp://tardis.tiny-vps.com/aarm/ā€ sometimes work, sometimes doesnā€™t.

9

check /var/cache/pacman/pkg/. The last 3 archived packages are here.

Package (4)          Old Version  New Version  Net Change

mesa                 1:24.3.1-3   1:24.2.7-1    15.76 MiB
opencl-rusticl-mesa  1:24.3.1-3   1:24.2.7-1    -2.32 MiB
vulkan-broadcom      1:24.3.1-3   1:24.2.7-1    -0.13 MiB
vulkan-mesa-layers   1:24.3.1-3   1:24.2.7-1    -0.45 MiB
10

I can confirm that after downgrading the ā€œmesaā€ package, the 3d rendering issue of Chromium has been resolved. I put a ā€œignorepkgā€ tag to mesa for the time being. So yeah, thanks for the quick help.

1 Like
11

Then we need a volunteer to make a bug report to mesa gitlabā€¦

14

So i see that in your list, you reverted not just ā€œmesaā€ but three more packages. Should i also revert the others like you did?

15

I would say that mixing packages in this case can lead to problems

17

I filed a bug report. Hopefuly the information will be enough. Could not post any logs though.

18

mesa-24.3.1 was 2 version behind ā†’ 24.3.3

19

iā€™m more or less in the same boat as you but on x86. iā€™m unaware of the branches you are in, but ā€˜unstableā€™ just upgraded to llvm-libs 19.x. mesa 24.2.7 explicitly depend on llvm 18, so when that upgrade to llvm hits you, you will have issues (in my case chrome didnt even start, basically anything depending on mesa stack will fail). so when you get the upgrade to llvm-libs 18.x ā†’ 19.x update, you will have to additionally install llvm18-libs to keep everything functional.

iā€™m not sure whether i can relate the issues iā€™ve been having with yours since we are on different platforms (x86 vs ARM), but for information sake, can you share the links to you prospective bugs for referral.

20
1 Like
21

mesa 24.3.3
Could you test. Warning after the upcoming update (clang et llvm) this mesa will not work.
Patch included
Could you correct the title itā€™s more mesa 24.3 render problem