Status: Untriaged Owner: [email protected] Labels: Type-Bug Pri-2 OS-All Area-Misc Size-Medium
New issue 15759 by [email protected]: Worker process does not get killed when GC collects the Worker object in the renderer. http://code.google.com/p/chromium/issues/detail?id=15759 Repro: 1. download attached files, load test.html in Chrome 2. Click 'Create worker' button. This creates a worker but does not keep the reference around so it's eligible for GC. 3. Observe the worker process created. 4. (Optional) Attach to renderer process and set breakpoint to Worker::~Worker() to see when a worker is destroyed. 5. Click "Create lots of strings" button, maybe more then once - to cause GC to happen. The ~Worker() is executed. However, the worker process is still around. It should be terminated. Attachments: worker.js 22 bytes test.html 492 bytes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
