-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome crashing on startup on TaskCluster #28209
Comments
Last successful run on master: https://community-tc.services.mozilla.com/tasks/groups/LrP_5K24Sj2GbBqettnASQ First failing run on master: https://community-tc.services.mozilla.com/tasks/groups/Hr2Ik-iXS6ivgZJfBWsn-Q There's definitely a chrome update here, from:
https://chromium.googlesource.com/chromium/src/+log/91.0.4449.0..91.0.4455.0?pretty=fuller&n=10000 should be the changelog I think, but it's pretty long. |
If needed, we should be able to pin Chrome Dev to |
Note that |
This is strange: I started trying to bisect in #28211, but the most recent build (865011) does not seem to exhibit the crash. (Technically 91.0.4455.2 is 865012 but there's no chrome-linux.zip for that currently). I'm not immediately sure what to conclude from that >_< |
This is a temporary measure while the cause of the crash is being investigated. This follows a similar approach taken before: #19360 Mitigation (not fix) for :wqhttps://github.com//issues/28209.
…9.6, a=testonly Automatic update from web-platform-tests [Taskcluster] pin Chrome Dev to 91.0.4449.6 (#28238) This is a temporary measure while the cause of the crash is being investigated. This follows a similar approach taken before: web-platform-tests/wpt#19360 Mitigation (not fix) for web-platform-tests/wpt#28209. -- wpt-commits: c89882cb8571e454e0643c3584206a48f9b37049 wpt-pr: 28238
I've sent a revert in #28464 now and it looks like the problem is gone. So we didn't need to investigate :) |
Fixed by #28464. |
This has begun happening again, reported by @jgraham: |
It has begun crashing on startup in 92.0.4484.7 and 91.0.4472.19 is the last version where it worked: #28209 (comment) Mitigation (not fix) for #28209.
https://chromium.googlesource.com/chromium/src/+log/91.0.4472.19..92.0.4484.7?n=10000 is huge so there's little hope of pinpointing this by just looking at the logs. @stephenmcgruer did you ever manage to bisect an issue like this by building a binary from the chromium tree and putting it in Taskcluster? |
It has begun crashing on startup in 92.0.4484.7 and 91.0.4472.19 is the last version where it worked: #28209 (comment) Mitigation (not fix) for #28209.
@foolip Yes. You can start without building Chromium yourself:
This will print URLs like Bisecting builds like this usually gets you to a few dozen changes. If things are still unclear at that point you can switch to local Chromium builds - basically you need to do a build, zip it (you don't need every output file, but you do need more than just the |
…2.19, a=testonly Automatic update from web-platform-tests [Taskcluster] pin Chrome Dev to 91.0.4472.19 It has begun crashing on startup in 92.0.4484.7 and 91.0.4472.19 is the last version where it worked: web-platform-tests/wpt#28209 (comment) Mitigation (not fix) for web-platform-tests/wpt#28209. -- wpt-commits: 8bc9fdfd1dfdd7303ed2753029f0f5f4db10e70e wpt-pr: 28661
Thanks @stephenmcgruer! That makes a lot of sense, but also sounded like work, so I procrastinated util now and have just sent #28902 to see if the issue has maybe magically resolved itself. If it hasn't, I'll have to do some bisecting :/ |
Nope, the problem has not been fixed, so I'm in for some debugging... |
I've filed https://bugs.chromium.org/p/chromium/issues/detail?id=1208904 to hopefully get some help from GPU experts in Chromium. Not really knowing what else to try, I've also sent #28992 to see how much the results change if we just use headless Chrome. That is a well-maintained way of running Chrome without a real GPU, after all. |
This should allow unpinning Chrome to the latest version, but it's first done while keeping the version pinned to vet the differences. Part of #28209.
This should allow unpinning Chrome to the latest version, but it's first done while keeping the version pinned to vet the differences. Part of #28209.
This should allow unpinning Chrome to the latest version, but it's first done while keeping the version pinned to vet the differences. Part of #28209.
This should allow unpinning Chrome to the latest version, but it's first done while keeping the version pinned to vet the differences. Part of #28209.
Chrome Dev is now running the latest version again. Diff: |
… version used on Taskcluster, a=testonly Automatic update from web-platform-tests Introduce an --enable-swiftshader argument for Chrome This should allow unpinning Chrome to the latest version, but it's first done while keeping the version pinned to vet the differences. Part of web-platform-tests/wpt#28209. -- Revert "[Taskcluster] pin Chrome Dev to 91.0.4472.19" This reverts web-platform-tests/wpt#28661. This requires updating infrastructure/server/context.any.js expectations. -- wpt-commits: b0e65e62d150a0cd1556dd7266aad765c49fe0d6, 8ebb14dc93f18c6558faa1608378df64ca4ee72f wpt-pr: 29095
… version used on Taskcluster, a=testonly Automatic update from web-platform-tests Introduce an --enable-swiftshader argument for Chrome This should allow unpinning Chrome to the latest version, but it's first done while keeping the version pinned to vet the differences. Part of web-platform-tests/wpt#28209. -- Revert "[Taskcluster] pin Chrome Dev to 91.0.4472.19" This reverts web-platform-tests/wpt#28661. This requires updating infrastructure/server/context.any.js expectations. -- wpt-commits: b0e65e62d150a0cd1556dd7266aad765c49fe0d6, 8ebb14dc93f18c6558faa1608378df64ca4ee72f wpt-pr: 29095
This is blocking all PRs.
A log excert from a recent master run:
@foolip
The text was updated successfully, but these errors were encountered: