New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 742308 link

Starred by 1 user
Status: Duplicate
Merged: issue 740873
Owner: ----
Closed: Jul 2017
Cc:
█ sandeepkumars@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

An issue with large memory consumption on form submit when hidden input with large base64 data is located in a form with "multipart/form-data"

Reported by supp...@devexpress.com, Jul 13 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0

Steps to reproduce the problem:
Open your Task Manager's Performance tab. Run the attached ASP.NET WebForms project and click the submit button. Watch the Memory state in the Task Manager's Performance tab while submitting the form.

What is the expected behavior?
The form should be submitted successfully with an acceptable memory consumption without Chrome crashing

What went wrong?
After this form submit, the operative memory consumption increases up to 2-3 gigabyte and Chrome crashes once the total operative memory size is reached.
See the attached video file.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: Version 59.0.3071.115 (Official Build) (64-bit)  Channel: n/a
OS Version: 8.1
Flash Version: Shockwave Flash 26.0 r0

We reproduced this problem in scenarios when a hidden input is located in a form with "multipart/form-data". Chrome crashes on the form submit when this input's value is set to a large base64 string on the server side.
We reproduced this issue with base64 strings with size about 3MB. The same scenario works correctly in other browsers without such memory leaks.
/Test_Chrome.zip
4.0 MB Download
/Chrome_memory_issue.swf
2.1 MB Download

Comment 1 by sandeepkumars@chromium.org, Jul 14 2017

Labels: Needs-Feedback
Thanks for the reprot.

@Reporter: Could you please attach the above files in accessible format to reprodcue the issue from our end as we are not able to access the above attched files.

Thanks!!

Comment 2 by tasak@google.com, Jul 14 2017 

Is this the same issue as  http://crbug.com/740873  ?

Comment 3 by supp...@devexpress.com, Jul 14 2017 

Hello,
 
I've reattached these files to the comment. The strange thing is that when I attached them to the issue, they had the correct .zip and .swf formats. But currently they are opened as .dat files.
If you still have problems with these files, please try to change these files' extension manually to .zip and .swf in order to see their content.
 
Regarding the second comment, indeed, the problem I described is quite similar to the  http://crbug.com/740873  issue. They seem to be caused by the same reason.
Test_Chrome.zip
4.0 MB Download
Chrome_memory_issue.swf
2.1 MB Download
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 14 2017

Cc: sandeepkumars@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 5 by sandeepkumars@chromium.org, Jul 14 2017

Mergedinto: 740873
Status: Duplicate (was: Unconfirmed)
Closing this issue as per comment #3. Please feel free to undupe if not the case.

Thanks!!

Comment 6 by supp...@devexpress.com, Jul 14 2017 

Thank you for your response. We will track that thread to get information about results regarding this issue.
►

Sign in to add a comment