Issue 859803 link

Starred by 2 users

Issue metadata

Status:	Duplicate
Merged:	issue 594950
Owner:	jarhar@chromium.org
Closed:	Nov 9
Components:	Platform>DevTools>Network
EstimatedDays:	----
NextAction:	----
OS:	Windows
Pri:	2
Type:	Bug
Needs-Feedback Arch-x86_64 Via-Wizard-DeveloperTools Triaged-ET Needs-Triage-M69

limit websocket capture buffer by size / amount

Reported by jeromin....@gmail.com, Jul 3

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3472.3 Safari/537.36

Steps to reproduce the problem:
1. open devtools
2. opening a website with many websocket messages
3. leaving the page open for a few hour

What is the expected behavior?

What went wrong?
The devTools are capturing all websocket messages when the window is open, which is a good thing. 
But there is no limit of capturing data, all is held in memory. 

Our application can run inside Visual Studio with CEF. This combination is limited to 32 bit, so the whole VS devenv.exe crashes after the memory has reached 3.x GBytes.

Since #647240 we can clear the frames, but the users can be not aware of the huge memory usage.

Perhaps the devTools needs to delete the oldest messages when the memory is used too much.

related 
#594950
but different as the messages are small so devTools is working fast
#834436 disabling capture is not wanted in some cases

Did this work before? No 

Chrome version: 69.0.3472.3  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:

Comment 1 by krajshree@chromium.org, Jul 4

Labels: Needs-Triage-M69

Comment 2 by viswa.karala@chromium.org, Jul 5

Cc: eostroukhov@chromium.org
Labels: Triaged-ET Needs-Feedback

Thanks for filing the issue!

@Reporter: Could you please provide sample test file/URL that reproduces the issue whcih help in further triaging the issue. Hence adding Needs-Feedback label to it.

Note: With reference to the Issues:  647240 , 594950,  834436 (provided in comment# 0), CC'ing the owner(eostroukhov@chromium.org) for further inputs on this issue.

Thanks!

Comment 3 by paulir...@chromium.org, Jul 9

Components: -Platform>DevTools Platform>DevTools>Network
Status: (was: Unconfirmed)

Comment 4 by jeromin....@gmail.com, Jul 18

I attached a small node websocket server which answers every request with a unique 900 kByte string.
The client.html has a logic which connects to the server, sends a message to it in a loop and counts this messages on the page.

Without devTools the memory usage of chrome is fine.
But opening devTools, switch to network tab, reload page, click button
=> devtools is beeing closing after a few gbytes of memory.
processexplorer performance graph is attached.