New issue
Advanced search Search tips

Issue 755940 link

Starred by 7 users
Status: Available
Owner: ----
Cc:
yhirano@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 3
Type: Bug



Sign in to add a comment

XMLHttpRequest crash tab when post file bigger than 150mb

Reported by t.belous...@dglogik.com, Aug 16 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
1. run example at https://codepen.io/tbelousova/pen/wqPQbE
2. select file bigger than 150mb
3. wait for while till tab crash

What is the expected behavior?
No tab crash

What went wrong?
Tab is crashed, probably due to running out of memory (new Chrome helper process with massive memory consumption)

Did this work before? N/A 

Chrome version: 60.0.3112.90  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

Tab is crashed in Windows and Mac Chrome. Nothing happens in Safari 10.1.2, Firefox 53.0.3

Comment 1 by bokan@chromium.org, Aug 16 2017

Components: -Blink Blink>Forms>File
Labels: OS-Linux
Status: Untriaged (was: Unconfirmed)
In a debug build on Linux I see:

[19926:19957:0816/080156.652423:ERROR:channel.cc(644)] Invalid message size: 460856928
[19926:19957:0816/080156.652585:ERROR:render_process_host_impl.cc(4090)] Terminating render process for bad Mojo message: Channel received a malformed message
[19926:19957:0816/080156.652646:ERROR:bad_message.cc(23)] Terminating renderer for bad IPC message, reason 123
[19926:19926:0816/080156.840487:WARNING:sad_tab.cc(278)] Tab Killed: https://codepen.io/

Looks like we're trying to send the file over in one big IPC.

Comment 2 by tkent@chromium.org, Aug 17 2017

Components: -Blink>Forms>File Blink>FileAPI Blink>Network
It looks a FileReader issue, or an XHR issue.

Comment 3 by ricea@chromium.org, Aug 17 2017

Cc: yhirano@chromium.org
Components: -Blink>FileAPI Blink>Loader
Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)
In this case the file is completely loaded into an ArrayBuffer before the request is issued, so it's not a problem with FileReader.

As said in #1, the problem is that we're sending the ArrayBuffer in one ResourceHostMsg_RequestResource IPC, and there's a 128MB IPC limit.

This could be fixed in the XMLHttpRequest code by turning large ArrayBuffers into a Blob or something like that, or more generally in the loader code.
Project Member

Comment 4 by sheriffbot@chromium.org, Aug 20

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by yhirano@chromium.org, Aug 22

Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)

Comment 6 by sharma0...@gmail.com, Sep 11 

Please fix it!!!!! Its breaking our system and very critical to get it fixed ASAP..
►

Sign in to add a comment