On 2023-06-12, Michael <confabul...@kintzios.com> wrote: >> It seems to be a variation on this bug which affects only AMD GPUs: >> >> https://bugs.gentoo.org/907431 >> >> Clearing the GPU driver cache or using the >> -disable-gpu-driver-bug-workarounds option avoids the problem. >> >> In my case, It wasn't a mesa update that triggered the problem. I >> think it was the llvm update (I haven't confirmed that). > > Did you (re)compile anything graphics related using llvm, which > might be used by the Chrome binary?
No -- but as I understand it, mesa uses llvm (at runtime) to generate GPU object code. Based on the work-around, it looks like compiled GPU object code is cached by Chrome/Chromium, and updates to mesa and/or llvm can result attempts to use old, incompatible GPU object code. As pages are rendered, there was a constant stream of "link failure" messages on the console window where Chrome is running. > I don't have chrome/chromium installed here to directly compare > notes and so far qtwebengine appears to work fine after updating > llvm this morning, as does www-client/microsoft-edge. Firefix-bin still worked fine also. It only seemed to affect Chrome/Chromium or it's derivitives. -- Grant
