[Webkit-unassigned] [Bug 139851] JSC::VM::m_lastStackTop initialized incorrectly when on non-main fiber; runaway memory corruption

[bugzilla-daemon at webkit.org]

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

Michael Saboff <msaboff at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #4 from Michael Saboff <msaboff at apple.com> ---
As was discussed, there isn't a know thread initialization issue for VM::m_lastStackTop.

WebKit in general and JavaScriptCore in particular does not support Windows fibers and would require work beyond just manage the saved last stack top to support fibers.

*IF* an application uses WebKit and takes advantage of fibers, it is the application's responsibility to make sure that WebKit sees only one and the same fiber per thread.  This includes that any fiber that calls into WebKit, including JavaScriptCore must not change what thread the fiber executes in.  All other fibers in a thread cannot make WebKit calls.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150105/30b79644/attachment-0002.html>