Bug 106016
| Summary: | [Qt] New fast/workers/worker-document-leak.html fails | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Csaba Osztrogonác <ossy> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | dimich, hausmann, kbr, ossy |
| Priority: | P2 | Keywords: | Qt, QtTriaged |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 87008, 105367 | ||
Csaba Osztrogonác
fast/workers/worker-document-leak.html introduced in https://trac.webkit.org/changeset/138693,
but fails on Qt with the following diff:
--- /ramdisk/qt-linux-64-release/build/layout-test-results/fast/workers/worker-document-leak-expected.txt
+++ /ramdisk/qt-linux-64-release/build/layout-test-results/fast/workers/worker-document-leak-actual.txt
@@ -1,4 +1,4 @@
Verify that creation of a worker does not leak its creating document.
-PASS: did not leak documents during test run
+FAIL: leaked documents during test run (started with 1, ended with 3)
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Csaba Osztrogonác
I skipped it to paint the bots green: r138710. Please unskip it with the proper fix.
Kenneth Russell
I don't know how to build the Qt port on any platform, so unfortunately can't help debug what's going on. You could try adding more calls to gc() at the end of the test, to try to force collection of the objects associated with the worker and the iframe's DOM.
Qt uses JSC, correct? Since it does, I'd expect it to behave similarly to the Mac port with respect to garbage collection of JavaScript wrappers. The new test seems to be passing on all the Mac bots.
Jocelyn Turcotte
=== Bulk closing of Qt bugs ===
If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.
If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.