Closed Bug 1915499 Opened 6 months ago Closed 6 months ago

[wpt-sync] Sync PR 47850 - [wptrunner] Implement `--leak-check` for Blink-based browsers

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox131 fixed)

RESOLVED FIXED
131 Branch
Tracking Status
firefox131 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 47850 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/47850
Details from upstream follow.

Jonathan Lee <jonathanjlee@google.com> wrote:

[wptrunner] Implement --leak-check for Blink-based browsers

... to support Chromium CI testing needs.

  • Introduce LeakProtocolPart, an optional API that lets wptrunner check for leaks programmatically. The default implementation checks that navigating to about:blank after a test cleans up the DOM objects it created.
  • For browsers that implement LeakProtocolPart, the base WebDriver executors run the leak check after each test and report the results as an extra test result field named leak_counters.
  • Currently, the only implementers of LeakProtocolPart are ChromeDriver-based browsers, which use a nonstandard Chrome DevTools Protocol method to count DOM objects. For those browsers, a leak is coerced to CRASH to report the result appropriately and induce a browser restart.

See Also: https://crbug.com/40887057

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a91a69df86fd [wpt PR 47850] - [wptrunner] Implement `--leak-check` for Blink-based browsers, a=testonly
Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → 131 Branch
You need to log in before you can comment on or make changes to this bug.