Bug 169713
| Summary: | WebAssembly: Allocating a fast memory is a bit racy | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Saam Barati <saam> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | benjamin, fpizlo, ggaren, gskachkov, jfbastien, keith_miller, mark.lam, msaboff, ticaiolima, ysuzuki |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=170628 | ||
Saam Barati
e.g, checking the allocatedFastMemories integer can be racy. We probably need more fine grained locking around parts of that algorithm.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
JF Bastien
I think resizing.wast.js runs into that issue. On ARM64 it'll segfault half the time for me.
JF Bastien
*** This bug has been marked as a duplicate of bug 170628 ***