MaxMemoryInitialPages is incorrect
Categories
(Core :: JavaScript: WebAssembly, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: lth, Assigned: rhunt)
References
Details
Attachments
(1 file, 1 obsolete file)
The spec says that the max number if initial pages is 32K, but our code uses 16K. This does not seem to have been a problem in practice, which is perhaps a useful data point in connection with the discussion about MaxInitial / MaxMaximum memory length: code does not in practice set the heap initial at very large values.
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
The spec no longer has an initial memory size limit, so we should allow up to
the limit imposed upon us by ArrayBuffer.
Depends on D80139
Assignee | ||
Comment 3•5 years ago
|
||
The spec no longer has an initial memory size limit, so we should allow up to
the limit imposed upon us by ArrayBuffer.
Depends on D80750
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Backed out for SM bustages on limits.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/1764e49f51f9d37c719427c10e959b31040ee023
Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=307475273&repo=autoland&lineNumber=42256
Assignee | ||
Comment 6•5 years ago
|
||
See bug 1642940 for info on the error's cause.
Comment 8•5 years ago
|
||
bugherder |
Description
•