Closed
Bug 1741465
Opened 3 years ago
Closed 3 years ago
Support reading files larger than UINT32_MAX bytes if we are reading at an offset
Categories
(Toolkit Graveyard :: OS.File, enhancement, P3)
Toolkit Graveyard
OS.File
Tracking
(firefox96 fixed)
RESOLVED
FIXED
96 Branch
Tracking | Status | |
---|---|---|
firefox96 | --- | fixed |
People
(Reporter: beth, Assigned: beth)
Details
Attachments
(1 file)
Currently if we want to read a file that is UINT32_MAX + N bytes from offset N, we will error out even though we can read that much data into a TypedArray.
Assignee | ||
Comment 1•3 years ago
|
||
Pushed by brennie@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b6ebaaea0102
Support reading files larger than UINT32_MAX if using a large enough offset r=Gijs
Comment 3•3 years ago
|
||
Backed out changeset b6ebaaea0102 (Bug 1741465) for causing bustages in IOUtils.cpp
Backout link: https://hg.mozilla.org/integration/autoland/rev/a94d331487a16ec105425c34badeb25545d0adbe
Push with failures, failure log.
Flags: needinfo?(brennie)
Assignee | ||
Updated•3 years ago
|
Flags: needinfo?(brennie)
Pushed by brennie@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a9b37651ccc7
Support reading files larger than UINT32_MAX if using a large enough offset r=Gijs
Comment 5•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox96:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
Updated•2 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•