Closed Bug 1714681 Opened 3 years ago Closed 3 years ago

Broken menu popups with gfx.xrender.enabled=true

Categories

(Core :: Graphics: WebRender, defect)

defect

Tracking

()

RESOLVED FIXED
91 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox89 --- wontfix
firefox90 --- fixed
firefox91 --- fixed

People

(Reporter: Oriol, Unassigned)

References

(Regression)

Details

(Keywords: crash, regression)

Crash Data

Attachments

(3 files)

  1. Set gfx.xrender.enabled=true. May require a restart.
  2. Click the hamburg menu

Expected: you see the menu
Actual: just some white area

Regression window: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=62e5068e45fd905fdb563245cad4efec1d8c0ac0&tochange=1646c323910d1f2438a60d9326903acf443542b9. That's bug 1699224.

I have Lubuntu 18.04.

Flags: needinfo?(aosmond)
Attached image firefox-crash.gif

BTW, the exit button in the hamburguer menu still seems to do its job even when you can't see it.
But if you click a bit above that (the help button, I guess), then Firefox crashes.
https://crash-stats.mozilla.org/report/index/7d7991b8-5ab5-470e-b84c-9dbfe0210606

Crash Signature: [@ __memmove_avx_unaligned_erms | Clamp_S32_D32_nofilter_trans_shaderproc ]
Keywords: crash

Can we get a severity set to this bug? Is that something common enough that we should work on a fix for 90 or for an 89 dot release? Thanks

Flags: needinfo?(jmathies)

XRender is not enabled by default so I wouldn't think this should require a dot release. Though uplifting a fix for 90 may make sense.

Oriol, could you please attach a copy of your about:support information? I presume the rendering issue only occurs with xrender enabled, but is that also the case for the crash in comment 1?

Severity: -- → S3
Flags: needinfo?(oriol-bugzilla)
Flags: needinfo?(oriol-bugzilla)
Attached file graphics-info.txt

That's my graphics info anyways, taken from 2021-06-09 (which includes the fix).

The crash in comment 1 required gfx.xrender.enabled=true and is also fixed now.

Great. That what I hoped would happen.

As an aside, why do you use gfx.xrender.enabled?

Flags: needinfo?(oriol-bugzilla)
Flags: needinfo?(jmathies)
Flags: needinfo?(aosmond)

OK, also fixed in beta https://hg.mozilla.org/releases/mozilla-beta/rev/e33597d2ca99eef625b927c646ebcc4840c80de3

(In reply to Jeff Muizelaar [:jrmuizel] from comment #6)

As an aside, why do you use gfx.xrender.enabled?

I don't remember, I just had it enabled for some reason, and when updating to 89 I noticed the menus were broken.

Flags: needinfo?(oriol-bugzilla)

(In reply to Oriol Brufau [:Oriol] from comment #4)

The problem has been fixed in https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a60835242de7a032a0223f906a96569dcfe82d52&tochange=808da1d9c00b1efe8affbd64702ed6155e612f96

That's bug 1712047, which I don't have access to. Please make sure to uplift it.

The patch has already landed in beta, and will ride along for a dot release. Marking this as fixed.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

(In reply to Oriol Brufau [:Oriol] from comment #7)

OK, also fixed in beta https://hg.mozilla.org/releases/mozilla-beta/rev/e33597d2ca99eef625b927c646ebcc4840c80de3

(In reply to Jeff Muizelaar [:jrmuizel] from comment #6)

As an aside, why do you use gfx.xrender.enabled?

I don't remember, I just had it enabled for some reason, and when updating to 89 I noticed the menus were broken.

I'd suggest turning it off. It's not a configuration that we want to support.

Crash Signature: [@ __memmove_avx_unaligned_erms | Clamp_S32_D32_nofilter_trans_shaderproc ] → [@ __memmove_avx_unaligned_erms | Clamp_S32_D32_nofilter_trans_shaderproc ] [@ __memcpy_sse2_unaligned_erms | Clamp_S32_D32_nofilter_trans_shaderproc ]
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: