Closed Bug 1553693 Opened 5 years ago Closed 4 years ago

Intermittent browser/base/content/test/performance/browser_startup_syncIPC.js | unexpected PAPZInputBridge::Msg_ProcessUnhandledEvent sync IPC before handling user events -

Categories

(Firefox :: General, defect, P5)

defect

Tracking

()

RESOLVED FIXED
Firefox 75
Tracking Status
firefox-esr68 --- unaffected
firefox73 --- unaffected
firefox74 --- unaffected
firefox75 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: kats)

References

(Regression)

Details

(Keywords: intermittent-failure, regression)

Filed by: ncsoregi [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=247848566&repo=autoland
Full log: https://queue.taskcluster.net/v1/task/QbMn9gdwTDuc26RfoLaxrQ/runs/1/artifacts/public/logs/live_backing.log


22:58:57 INFO - TEST-PASS | browser/base/content/test/performance/browser_startup_syncIPC.js | sync IPC PAPZInputBridge::Msg_ProcessUnhandledEvent happened as many times as expected before first paint -
22:58:57 INFO - whitelisted sync IPC before handling user events:
22:58:57 INFO - PLayerTransaction::Msg_GetTextureFactoryIdentifier - at most 1 times
22:58:57 INFO - PCompositorBridge::Msg_Initialize - at most 1 times
22:58:57 INFO - PCompositorBridge::Msg_WillClose - at most 1 times
22:58:57 INFO - PCompositorBridge::Msg_MakeSnapshot - at most 1 times
22:58:57 INFO - Buffered messages finished
22:58:57 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_startup_syncIPC.js | unexpected PAPZInputBridge::Msg_ProcessUnhandledEvent sync IPC before handling user events -
22:58:57 INFO - Stack trace:
22:58:57 INFO - chrome://mochikit/content/browser-test.js:test_ok:1314
22:58:57 INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/browser_startup_syncIPC.js:null:226
22:58:57 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1116
22:58:57 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1144
22:58:57 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:1005
22:58:57 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:803
22:58:57 INFO - Not taking screenshot here: see the one that was previously logged
22:58:57 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_startup_syncIPC.js | unexpected PAPZInputBridge::Msg_ReceiveMouseInputEvent sync IPC before handling user events -
22:58:57 INFO - Stack trace:
22:58:57 INFO - chrome://mochikit/content/browser-test.js:test_ok:1314
22:58:57 INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/browser_startup_syncIPC.js:null:226
22:58:57 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1116
22:58:57 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1144
22:58:57 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:1005
22:58:57 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:803

FYI test has been disabled

Flags: needinfo?(florian)

(In reply to Kartikaya Gupta (email:kats@mozilla.com) (away until Feb-2020) from comment #16)

FYI test has been disabled

Thanks! This bug was for an intermittent failure. The perma failure that caused the test to be disabled on asan was filed as bug 1574535.

Flags: needinfo?(florian)

I take a look.

Assignee: nobody → sotaro.ikeda.g
Flags: needinfo?(sotaro.ikeda.g)

I wonder if the failure might be triggered by timing change, since the intermittent failure already existed. Bug 1554610 added unnecessary compositor window shutdown. It could change the timing.

CompositorBridgeParent::AllocPLayerTransactionParent() creates unnecessary compositor window when creating basic compositor during d3d compositor is available. It seems better to avoid to create unnecessary compositor window.

Depends on: 1616174

It seems that amount of intermittent was dropped by Bug 1616174 .

Assignee: sotaro.ikeda.g → nobody

Update, this has:

It fails only on windows opt jobs as it's skipped on ((os == 'win') && asan) || (os == 'linux' && bits == 64 && os_version == '18.04') https://searchfox.org/mozilla-central/source/browser/base/content/test/performance/io/browser.ini#23
Recent failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=286799353&repo=mozilla-central
Sotaro, do you mind having another go at this? Thank you.

Flags: needinfo?(sotaro.ikeda.g)

I do not know well about PAPZInputBridge::Msg_ProcessUnhandledEvent. :kats and :botond know better than me.

Flags: needinfo?(sotaro.ikeda.g) → needinfo?(kats)
Flags: needinfo?(botond)

I can look

Assignee: nobody → kats
Flags: needinfo?(kats)
Flags: needinfo?(botond)

Put a patch on bug 1619299 which should fix the majority of these failures (all the ones dealing with APZInputBridge). There might be other failures but it should be much lower volume. I'll keep this bug open to track any other problems after bug 1619299 lands.

Bug 1619299 seems to have worked as intended, the volume here is basically zero since that landed. I'll leave this bug open a bit longer to confirm.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 75
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.