New issue
Advanced search Search tips

Issue 808400 link

Starred by 1 user
Status: WontFix
Owner:
yukishiino@chromium.org
Closed: Feb 2018
Cc:
ricea@chromium.org
lfg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 2
Type: Bug



Sign in to add a comment

[Missing Test]:Continuously sending larger amounts of data over a WebSocket connection causes Chrome to use up a lot of memory and eventually crash.

Project Member Reported by vamshi.k...@techmahindra.com, Feb 2 2018 
Automated tests for the below commit have been missing.Would it be possible to add test coverage to avoid regressions in future?

CL: 
----   https://chromium.googlesource.com/chromium/src.git/+/dbbb53737fe037d6b6f54a9a6114670149a55cd1


Ref Bug: 
---------
https://bugs.chromium.org/p/chromium/issues/detail?id=339480

yukishiino@ - Could you please take a look in to this issue?


Thanks!

Comment 1 by ricea@chromium.org, Feb 2 2018

Cc: ricea@chromium.org
It may not be possible to write a layout test that can exhaust memory on a wide range of machines in an acceptable amount of time. Maybe something is possible in a unit test?

Comment 2 by yukishiino@chromium.org, Feb 8 2018

Status: WontFix (was: Assigned)
This is hard to test.  One difficulty is how to exhaust memory.  The original issue report uses an external WebSocket server to send a bunch of messages.  If we tried the same thing from a web page, the web page itself consumes memory and it triggers GC.  I.e. we cannot reproduce the original issue (an external WebSocket server can send a bunch of messages without triggering renderer's GC, but layout tests cannot, nor it's not easy with even a unit test.)

So, I close this issue as WontFix.
►

Sign in to add a comment