Bug 169892 - WebAssembly: WasmMemory::lastAllocatedMemoryMode is racy
Summary: WebAssembly: WasmMemory::lastAllocatedMemoryMode is racy
Status: RESOLVED DUPLICATE of bug 170628
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 159775
  Show dependency tree / graph
 
Reported: 2017-03-20 14:11 PDT by JF Bastien
Modified: 2017-04-07 17:13 PDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description JF Bastien 2017-03-20 14:11:22 PDT 
It's a benign race... but you can create two Workers, use wasm, and they clobber the value independently.

I'm not sure TLS is the best thing either. Having the VM may be better?
Comment 1 JF Bastien 2017-03-20 14:15:24 PDT 
Same for allocatedFastMemories, though this one is less benign.
Comment 2 JF Bastien 2017-04-07 17:13:28 PDT 

*** This bug has been marked as a duplicate of bug 170628 ***