Closed Bug 1738977 Opened 3 years ago Closed 3 years ago

Window occlusion causes pages to not render on an external monitor

Categories

(Core :: Widget: Win32, defect)

Unspecified
Windows
defect

Tracking

()

VERIFIED FIXED
96 Branch
Tracking Status
firefox-esr91 --- unaffected
firefox93 --- unaffected
firefox94 --- unaffected
firefox95 --- unaffected
firefox96 + verified

People

(Reporter: cpeterson, Assigned: sotaro)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

@ Sotaro, this bug is a regression from enabling window occlusion in bug 1732736.

I bisected this regression to this pushlog for bug 1732736:

https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=4dc03a8a15db6385e71d7d4452bc2d24f7544a23&tochange=02ea2d15bf4c17c346aa9e06775c7027cdfacabf

In Nightly 96 build 2021-11-02, Firefox fails to load any web page. Tabs are blank/white.

I am running Windows 11 and have an external display attached to a laptop. I don't know if this is an API issue with Windows 11 or an issue with an external display. I will post my about:support info and test without my external display.

Flags: needinfo?(sotaro.ikeda.g)
Attached file about-support.txt (deleted) —

I confirmed setting widget.windows.window_occlusion_tracking.enabled pref = false fixes the problem.

This bug only affects pages that I attempt to load in a window on my external monitor. If I drag a window that an unrendered page from my external monitor to my laptop's monitor, the unrendered page is rendered immediately.

Assignee: nobody → sotaro.ikeda.g
Summary: Window occlusion causes pages to never load → Window occlusion causes pages to not render on an external monitor

Fixed by backout of bug 1732736. New Windows Nightlies have been requested.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch

I could reproduce the problem when 2nd display was set to main display. The problem happened on Win10 and on Win11.
Somehow, when 1st display was main display, I could not reproduce the problem on my PCs.

I am going to look into what caused the problem.

Flags: needinfo?(sotaro.ikeda.g)

I found the problem and created bug 1739310.

The following code is wrong. I made a mistake during porting the ComputeNativeWindowOcclusionStatus() from chromium to gecko.

https://searchfox.org/mozilla-central/rev/88cd13997fb0747cdcd78638fc762ff2d75e1fc5/widget/windows/WinWindowOcclusionTracker.cpp#920

Depends on: 1739310

:cpeterson, can you check if the problem is addressed for you with latest nightly with pref "widget.windows.window_occlusion_tracking.enabled" == true?

Flags: needinfo?(cpeterson)

(In reply to Sotaro Ikeda [:sotaro] from comment #8)

:cpeterson, can you check if the problem is addressed for you with latest nightly with pref "widget.windows.window_occlusion_tracking.enabled" == true?

widget.windows.window_occlusion_tracking.enabled == true works for me now. Thanks!

Verified fixed in Nightly 96.0a1 build 2021-11-04.

Status: RESOLVED → VERIFIED
Flags: needinfo?(cpeterson)

Good. Thank you!

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: