Closed Bug 1615434 Opened 5 years ago Closed 5 years ago

MaxMemoryInitialPages is incorrect

Categories

(Core :: JavaScript: WebAssembly, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla79
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.

See Also: → 1617821
Severity: normal → S3

I'm taking a look at this.

Assignee: nobody → rhunt

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

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

Attachment #9158711 - Attachment is obsolete: true
Pushed by rhunt@eqrion.net: https://hg.mozilla.org/integration/autoland/rev/068ffb754356 Increase maximum initial memory size to 2GiB. r=lth

See bug 1642940 for info on the error's cause.

Flags: needinfo?(rhunt)
Pushed by rhunt@eqrion.net: https://hg.mozilla.org/integration/autoland/rev/bd6573a5176d Increase maximum initial memory size to 2GiB. r=lth
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: