Closed Bug 1775927 Opened 2 years ago Closed 1 year ago

Intermittent docshell/test/browser/browser_browsingContext-webProgress.js | single tracking bug

Categories

(Core :: DOM: Navigation, defect, P3)

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
112 Branch
Tracking Flags:
Tracking Status
firefox112 --- fixed

People

(Reporter: jmaher, Assigned: farre)

References

Details

(Keywords: intermittent-failure, intermittent-testcase, Whiteboard: [stockwell unknown])

Attachments

(1 file)

Bug 1775927 - Make sure progress listener isn't gc'd. r=peterv!
48 bytes, text/x-phabricator-request
Details | Review
No description provided.

Additional information about this bug failures and frequency patterns can be found by running: ./mach test-info failure-report --bug 1775927

Update:

There have been 34 failures within the last 7 days:

  • 25 failures on Linux 18.04 x64 WebRender debug
  • 7 failures on OS X 10.15 WebRender debug
  • 1 failure on Windows 10 x86 2004 WebRender debug
  • 1 failure on Windows 10 x64 2004 WebRender debug

Recent failure log: https://treeherder.mozilla.org/logviewer?job_id=399953208&repo=autoland&lineNumber=4764

Edgar, can you help us assign this to someone?
Thank you.

Flags: needinfo?(echen)
Whiteboard: [stockwell needswork:owner]

Update:

There have been 31 failures within the last 7 days:

  • 23 failures on Linux 18.04 x64 WebRender debug
  • 8 failures on OS X 10.15 WebRender debug

Recent failure log: https://treeherder.mozilla.org/logviewer?job_id=402347162&repo=autoland&lineNumber=15994

Flags: needinfo?(htsai)

There have been 37 total failures in the last 7 days, recent failure log.
Affected platforms are:

  • linux1804-64-qr
  • macosx1015-64-qr
  • windows10-64-2004-qr
[task 2023-02-03T21:01:59.112Z] 21:01:59     INFO - TEST-PASS | docshell/test/browser/browser_browsingContext-webProgress.js | undefined assertion name - 
[task 2023-02-03T21:01:59.112Z] 21:01:59     INFO - Buffered messages finished
[task 2023-02-03T21:01:59.113Z] 21:01:59     INFO - TEST-UNEXPECTED-FAIL | docshell/test/browser/browser_browsingContext-webProgress.js | STATE_START, when navigating to another process, fires on the BrowsingContext we navigate *from* - Got [object CanonicalBrowsingContext], expected [object CanonicalBrowsingContext]
[task 2023-02-03T21:01:59.113Z] 21:01:59     INFO - Stack trace:
[task 2023-02-03T21:01:59.113Z] 21:01:59     INFO - chrome://mochikit/content/browser-test.js:test_is:1484
[task 2023-02-03T21:01:59.113Z] 21:01:59     INFO - chrome://mochitests/content/browser/docshell/test/browser/browser_browsingContext-webProgress.js:null:149
[task 2023-02-03T21:01:59.114Z] 21:01:59     INFO - TEST-PASS | docshell/test/browser/browser_browsingContext-webProgress.js | undefined assertion name -

There have been 33 total failures in the last 7 days, recent failure log.
Affected platforms are:

  • linux1804-64-qr
  • macosx1015-64-qr
  • windows10-32-2004-qr
  • windows10-64-2004-qr

Andreas, can you take a look at this frequent failure a bit? Thank you.

Flags: needinfo?(htsai)
Flags: needinfo?(echen)
Flags: needinfo?(afarre)
Assignee: nobody → afarre
Flags: needinfo?(afarre)

Reproduced in Pernosco.

There have been 39 total failures in the last 7 days.
There are:

  • 22 failures on linux1804-64-qr
  • 12 failures on macosx1015-64-qr
  • 3 failures on windows10-32-2004-qr
  • 2 failures on windows10-64-2004-qr
    All the failures are debug only.

Recent failure log.

Andreas, can you please take another look at this? Thank you

Flags: needinfo?(afarre)

nsIWebProgressListener is stored as a weak reference in
nsIWebProgress. To not have it garbage collected we need to keep a
reference to it.

This fixes most of the failures, in particular all of the ones that time out. I think we should keep this bug closed and open new issues for the remaining failures as they come in, instead of having a single tracking bug.

Flags: needinfo?(afarre)
Status: NEW → ASSIGNED

we will be switching soon to making single tracking bugs a meta bug where when a needinfo happens it will take place in a new bug to investigate, fix, disable, etc.; we want to keep single tracking bug for tooling that will help with sheriffing and autoclassification

Pushed by afarre@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b8377a7034c3
Make sure progress listener isn't gc'd. r=peterv

https://hg.mozilla.org/mozilla-central/rev/b8377a7034c3

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox112: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
See Also: → 1819591
See Also: → 1820127
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: