[Webkit-unassigned] [Bug 114652] Verify that r148475 didn't break the HeapTimer implementation for Qt

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=114652





--- Comment #1 from Allan Sandfeld Jensen <allan.jensen at digia.com>  2013-04-16 03:05:49 PST ---
Thanks for warning.

The important thing here is that the HeapTimer is destroyed by the owning thread/event loop. In Qt this is usually the thread where the object was created, but the HeapTimer is constantly migrated to the thread that holds the JS APILock. So as long as that is help when the delete happens, it should be fine.

If that doesn't happen. Things get more complicated. It should then be deleted using deleteLater() (to the let its own eventloop delete it), and would need some race-condition protection in the fire-handler similar to what you have for CF.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.