Bugzilla

Narrowed regression range after some gve tasks completed:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=aea58e5386eae7e197cfae9706804d22d8e3342c&tochange=c5ec87ff79c5e8faf3e69f4dd3057c1df36c49e7

I think that confirms bug 1881978 as the regressor.

(Note that the first and last pushes in that push-range were for landing and then backing out a particular bug  ( 1759175 ) -- that bug happened to trigger android build-bustage while it was in, so I suspect we can't bisect further. But also, we probably don't need to worry about bisecting further.)

(In reply to Glenn Watson [:gw] from comment #3)
> It's plausible that the change exposes some kind of driver / shader compiler bug.

Thanks.  I think it's not one that I can get an update for, unfortunately; this device is no longer getting OS updates (including from LineageOS which brought it another year or two into the future beyond where it would have otherwise been EOL'd).

I'm not sure how to assess how many folks might be affected by a similar driver bug & don't want to over-pivot based on my own device happening to be lucky enough to have a bug that exposed by a Firefox update.  I wonder if we should block-list my driver version (from comment 4 about:support info in comment 4)?

I did confirm that enabling software-webrender (`gfx.webrender.software = true`) fixes the bug for me, so I'll be using that on this device going forward.

Narrowed regression range after some gve tasks completed:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=aea58e5386eae7e197cfae9706804d22d8e3342c&tochange=c5ec87ff79c5e8faf3e69f4dd3057c1df36c49e7

I think that confirms bug 1881978 as the regressor.

(Note that the first and last pushes in that push-range were for landing and then backing out a particular bug  ( 1759175 ) -- that bug happened to trigger android build-bustage while it was in, so I suspect we can't bisect further. But also, we probably don't need to worry about bisecting further.)

(In reply to Glenn Watson [:gw] from comment #3)
> It's plausible that the change exposes some kind of driver / shader compiler bug.

Thanks.  I think it's not one that I can get an update for, unfortunately; this device is no longer getting OS updates (including from LineageOS which brought it another year or two into the future beyond where it would have otherwise been EOL'd).

I'm not sure how to assess how many folks might be affected by a similar driver bug & don't want to over-pivot based on my own device happening to be lucky enough to have a bug that was exposed by a Firefox update.  But I wonder if we should block-list my driver version (from comment 4 about:support info in comment 4)?

I did confirm that enabling software-webrender (`gfx.webrender.software = true`) fixes the bug for me, so I'll be using that on this device going forward.