| Summary: | WorkerContext.close() does not work in the chromium port | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Andrew Wilson <atwilson> | ||||
| Component: | WebCore JavaScript | Assignee: | Andrew Wilson <atwilson> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | commit-queue, dimich, levin | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | PC | ||||||
| OS: | OS X 10.5 | ||||||
| Attachments: |
|
||||||
Created attachment 48172 [details]
Patch
Comment on attachment 48172 [details] Patch Clearing flags on attachment: 48172 Committed r54380: <http://trac.webkit.org/changeset/54380> All reviewed patches have been landed. Closing bug. |
We do not shutdown the Worker thread in the chromium port when the thread calls close(). This means that code like this: var worker = new Worker("worker.js"); worker.js: close(); Will leave the thread running until the parent window shuts down. There's code in Chromium to prevent further messages from being to/from the closing thread, but the thread itself still sits there.