Bug 133251
| Summary: | Log an error to the console when using a WebKit-based JSContext from multiple threads | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Mark Hahnenberg <mhahnenberg> |
| Component: | JavaScriptCore | Assignee: | Mark Hahnenberg <mhahnenberg> |
| Status: | NEW | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Mark Hahnenberg
We set a particular flag in the JSLock for a VM when it's being used by WebKit. Some of our clients are tripping up over trying to use a WebKit-based JSContext on multiple threads. We could help them out by logging an error if we ever observe on a thread other than the main thread the use of a VM with a JSLock with the m_hasExclusiveThread field set.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |