gecko-dev/devtools/server/tests/browser/browser_markers-cycle-collection.js
yulia 1174ad2f82 Bug 1495389 - adjust test to use new performance front initialization; r=ochameau
Depends on D10564

Differential Revision: https://phabricator.services.mozilla.com/D11293

--HG--
extra : moz-landing-system : lando
2018-12-17 11:54:45 +00:00

29 lines
1 KiB
JavaScript

/* Any copyright is dedicated to the Public Domain.
http://creativecommons.org/publicdomain/zero/1.0/ */
/**
* Test that we get "nsCycleCollector::Collect" and
* "nsCycleCollector::ForgetSkippable" markers when we force cycle collection.
*/
"use strict";
add_task(async function() {
// This test runs very slowly on linux32 debug EC2 instances.
requestLongerTimeout(2);
const target = await addTabTarget(MAIN_DOMAIN + "doc_force_cc.html");
const front = await target.getFront("performance");
const rec = await front.startRecording({ withMarkers: true });
const markers = await waitForMarkerType(front,
["nsCycleCollector::Collect", "nsCycleCollector::ForgetSkippable"]);
await front.stopRecording(rec);
ok(markers.some(m => m.name === "nsCycleCollector::Collect"),
"got some nsCycleCollector::Collect markers");
ok(markers.some(m => m.name === "nsCycleCollector::ForgetSkippable"),
"got some nsCycleCollector::Collect markers");
await target.destroy();
gBrowser.removeCurrentTab();
});