[Webkit-unassigned] [Bug 28702] Workers do not exit after async operations
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Aug 27 11:57:07 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=28702
--- Comment #5 from Andrew Wilson <atwilson at chromium.org> 2009-08-27 11:57:06 PDT ---
After talking with ap on IRC:
1) The worker code refactoring broke setTimeout("code to evaluate") -
ScheduledAction.cpp invokes scriptController->evaluate(), and we no longer call
reportPendingActivity() from there (responsibility for doing this was moved to
the caller).
2) The setTimeout(function() {...}) code was already broken, since it never
went through WorkerScriptController.
3) XHR callbacks have always been broken AFAIK since they just invoke their
listener code directly and have never gone through WorkerScriptController.
It seems like the right solution is to have WorkerRunLoop::run() report pending
activity after each event is processed - any other solution seems fragile since
it requires extra work every time we add a new async operation (DB
transactions, appcache notifications, etc).
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list