Closed Bug 1313624 Opened 8 years ago Closed 6 years ago

Large 293MB XHR throws "allocation size overflow" error on accessing xhr.responseText

Categories

(Core :: JavaScript Engine, defect, P3)

49 Branch
x86_64
Windows 10
defect

Tracking

()

RESOLVED DUPLICATE of bug 1509542

People

(Reporter: jujjyl, Unassigned)

References

Details

(Keywords: triage-deferred)

STR:

1. Download http://clb.demon.fi/bugs/large_xhr_allocation_size_overflow/UnrealEngine4_Development_SafeHeap.7z

2. Uncompress (it is LZMA2), and run python -m SimpleHTTPServer in the directory, and open http://localhost:8000/MyProject.html in browser. (64-bit browser is preferred)

Observed:

Accessing the result of the XHR throws an exception "allocation size overflow" inside jQuery, when it is reading the xhr.responseText property. Happens on both FF Stable 49 and current Nightly.

Expected:

The test system has 32GB of RAM, it should easily be able to handle a 300MB JS file in a 64-bit browser. (not expecting this to not OOM on a 32-bit browser though)
"allocation size overflow" is a JS engine message, so tentatively -> JS Engine.

That file is probably in utf8, and the data will be converted to utf16, so 2x memory, but should still be fine.
Component: DOM → JavaScript Engine
Keywords: triage-deferred
Priority: -- → P3
Bug 1509542 should alleviate this by raising our string length limit.
Depends on: 1509542
I'll actually just close this as duplicate. Our limit is now 1 GB instead of 256 MB and is similar to Chrome. Good enough for now I expect.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.