Closed pjpreilly closed 2 years ago
chrome://gpu/
GPU process was unable to boot: GPU process crashed too many times with SwiftShader.
Is there a crash log from the GPU process?
GPU process was unable to boot: GPU process crashed too many times with SwiftShader.
Is there a crash log from the GPU process?
Not one that is repeatable by loading the page.
Not one that is repeatable by loading the page.
What about from when you first launch Chromium? If Chromium is disabling Swiftshader at launch, you presumably won't see a crash after launch.
This from the Aquarium website.....
What about from when you first launch Chromium? If Chromium is disabling Swiftshader at launch, you presumably won't see a crash after launch.
What about from when you first launch Chromium? If Chromium is disabling Swiftshader at launch, you presumably won't see a crash after launch.
I'm not sure the crash is necessarily related because it starts up with webgl disabled well before I try to run any...so.....
[24554:771:0809/134544.232532:ERROR:gl_implementation.cc(504)] Failed to load /Applications/Chromium.app/Contents/Frameworks/Chromium Framework.framework/Versions/106.0.5223.0/Libraries/libEGL.dylib: dlopen(/Applications/Chromium.app/Contents/Frameworks/Chromium Framework.framework/Versions/106.0.5223.0/Libraries/libEGL.dylib, 1): Library not loaded: /System/Library/Frameworks/Metal.framework/Versions/A/Metal
Referenced from: /Applications/Chromium.app/Contents/Frameworks/Chromium Framework.framework/Versions/106.0.5223.0/Libraries/libEGL.dylib
Reason: image not found
Well, uh, that would do it. Why does a software renderer require metal?!
Replacing Chromium.app/Contents/Frameworks/Chromium Framework.framework/Versions/106.0.5223.0/Libraries/libEGL.dylib
with the version from Chromium 104 (attached for convenience) fixes the problem, at least on 10.9.5.
Replacing
Chromium.app/Contents/Frameworks/Chromium Framework.framework/Versions/106.0.5223.0/Libraries/libEGL.dylib
with the version from Chromium 104 (attached for convenience) fixes the problem, at least on 10.9.5.
& Lion too..... I'm assuming this will be incorporated for future builds......thx... good work Columbo @Wowfunhappy
But I still get gpu crashes that are unrelated....here it is Columbo..... Still Crashes.txt
@Wowfunhappy should I open a new bug report..... for Still Crashes crash instance....
@pjpreilly Personally, I'd wait until a stable build to confirm. We also might want this issue to be fixed first, in case swapping with an old libEGL library is what's causing the crash.
If I go back to stable & can cause it...maybe then....
I always thought that WebGL never worked on these Chromium builds.
WebGL works, it's just done in software instead of hardware! (AIUI some small portion is also hardware accelerated in 10.9, just not "gpu compositing", I don't entirely understand what that means.)
Run this... https://webglreport.com/ Webgl 1 and Webgl 2
@Wowfunhappy on another topic... should I open a new bug report for an iSight regression that works in Stable but now fails in Canary?
@pjpreilly If it were me, I'd test if the webcam was broken in the closest available build of Chrome Canary first, to confirm it was a Chromium Legacy issue.
Closest to what....Canary closest to current Stable....or just go step by step back revisions in Canary until the works/breaks rev boundary is found....?
From the list of official Chromium builds here: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/
You want to test the two revisions that are closest to the latest Canary build of Chromium Legacy. So for example, since the last Chromium Legacy build is 1032258
, I would test 1032260
. If webcam functionality is broken there too, it's not a Chromium Legacy issue. If the webcam works, then we know it's a Chromium Legacy specific bug.
This does require a modern Mac or a VM. If you don't have access to that, it might be best to wait until the next stable.
Google Meet is causing Chromium Helper (Plugin) to crash in current Canary..... when trying to activate the camera....
Google Meet is causing Chromium Helper (Plugin) to crash in current Canary..... when trying to activate the camera....
That would seem to be a Chromium Legacy issue..?
That would seem to be a Chromium Legacy issue..?
Seems like it might be easily recreated by you.....
Then again could we have created this by patching the WebGl issue with the 104 libEGL.dylib work around...?
NOPE .... crashes without the patch too......
So like WebGl the latest version of Canary is the FIRST & only version where the iSight camera does not work......
So here's the isight crash log from the Meet camera failure....... Isight Meet Crash.txt
...& Google Meets camera works fine on Canary 106.0.5246.0 on a modern mac.....FWIW....
&.... both issues FIXED in 1036413....
Describe the bug
Webgl doesn't work on the latest canary build 1032258 ONLY. Works on all other Canary & Stable builds.
Steps to reproduce the behavior:
Expected behavior Fish swimming
Desktop (please complete the following information): macOS X Lion macbook 3,1 & macbook 4,1