Closed Bug 1856330 Opened 2 years ago Closed 2 years ago

With about:blank patch test_group_mouseevents.html turns from intermittent to perma orange

Categories

(Core :: Panning and Zooming, defect, P2)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: hsivonen, Unassigned)

References

Details

When the patch for bug 543435 is applied, https://searchfox.org/mozilla-central/source/gfx/layers/apz/test/mochitest/test_group_mouseevents.html turns into a permafailure.

Bug 1776963 is already on file for it failing intermittently.

When I've tried to resolve this, I've noticed that the test is very timing-sensitive: adding some logging to stdout can change timing enough to make the test pass when it fails without a logging statement. The patch adds a logging statement for "Printing something here to avoid failure". That actually helped with an earlier iteration of the patch for bug 543435 but no longer does.

Understanding this would benefit from a look by the graphics team.

Steps to reproduce

  1. Apply the patch for bug 543435
  2. Run the test gfx/layers/apz/test/mochitest/test_group_mouseevents.html

Setting the same priority/severity as bug 543435. I will look into detail the failure.

Severity: -- → S3
Flags: needinfo?(hikezoe.birchill)
Priority: -- → P2

Though I am not yet sure where the underlying problem is, I am sure that the patch for bug 543435 breaks our layout history state machinery.

The sub test name causing test_group_mouseevents.html timeout is helper_visualscroll_nonrcd_rsf.html. And the test in question reconstructs a sub document's root scrollable frame. And the during the reconstruction, we do get the last layout history state via this nsFrameConstructorState, but with the patch we somehow get null history state unfortunately.

CCing Henri.

Flags: needinfo?(hikezoe.birchill)

Thank you! It looks like nsDocShell::mActiveEntry is nullptr for the initial about:blank here. (When the test passes without the patch, the about:blank isn't the truly initial one but a second about:blank, which the patch is getting rid of.)

This works now. Thanks.

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

\o/

You need to log in before you can comment on or make changes to this bug.