Summary: | [Qt] 3 fast/workers test fails with timeout with LLInt if JIT is disabled | ||
---|---|---|---|
Product: | WebKit | Reporter: | Csaba Osztrogonác <ossy> |
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Critical | CC: | allan.jensen, fpizlo, gaborb, hausmann, loki, mark.lam, ossy, zherczeg |
Priority: | P1 | Keywords: | Qt, QtTriaged |
Version: | 420+ | ||
Hardware: | All | ||
OS: | All | ||
Bug Depends on: | |||
Bug Blocks: | 79668, 97584 |
Description
Csaba Osztrogonác
2012-11-04 00:41:27 PDT
Maybe they fail on other ports too, but I can't test on any port different from Qt. and fast/workers/worker-lifecycle.html fails if you run only fast/workers tests instead of all tests. +info: ------- - fast/workers/storage/interrupt-database.html passes if you run only this test, but it is extremely slow, the runtime is 12-18 seconds - fast/workers/worker-close-more.html fails always (if you run only this test or only fast/workers tests or all tests) - fast/workers/worker-lifecycle.html passes if you run only this test or all tests, but fails if you run fast/workers tests The bug is same on 32 and on 64 bit LLINT C loop. ping? I can reproduce the fast/workers/worker-close-more.html and fast/workers/worker-lifecycle.html notifyDone() timeouts on an ASM llint build with JIT & DFG disabled. This is not a C++ llint specific issue. Status report: - fast/workers/storage/interrupt-database.html: still extremely slow - fast/workers/worker-close-more.html: still fails always - fast/workers/worker-lifecycle.html: it passes now Is there any plan to fix LLInt? Or can we live with this buggy LLInt? (In reply to comment #5) > Status report: > - fast/workers/storage/interrupt-database.html: still extremely slow > - fast/workers/worker-close-more.html: still fails always > - fast/workers/worker-lifecycle.html: it passes now > > Is there any plan to fix LLInt? Or can we live with this buggy LLInt? I see these same failures when running the tests with a debug build using the JIT as well. This tells me that this isn't a matter of correctness, but perhaps of performance. Alternatively, it may be because the tests have timeouts that are too short. This issue is currently low on my priority list. You're welcome to debug it and provide suggestions for improvement or a patch though. === 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. |