Improve devtools network XHR capture to prevent OOM on long running debugging sessions |
||||
Issue descriptionFrom chat with joeyparrish@ today, long-running mediasource web app debugging sessions with devtools network window open to capture XHR network info can eventually crash due to OOM (because mediasource apps make lots of network XHR fetches for various segments of media; note that such requests are not differentiable as "media"). This bug is to investigate and implement options to mitigate such OOM crashing, such as (rough ideas): 1) Allow option to just retain network headers but not full response bodies, 2) switch to option 1 when memory pressure indicates it's needed?
,
Nov 2 2017
Another idea: I could also avoid OOM and still monitor what matters to me if I were able to apply a filter to the recording of network traffic, rather than just the view.
,
Nov 2 2017
IMHO c#2 is better than my option 1 because it would allow more flexible filtering options ideally (eg. retain headers and response body, but for only certain requests as defined in the custom filter).
,
Nov 3 2017
,
Dec 13 2017
DevTools will only collect up to 800Mb of data. What's the scenario for this? Have you seen OOM crashes? Was it on mobile?
,
Dec 13 2017
There has been a release or two since I tried, but it was consuming multiple gigabytes of RAM and crashed the tab. When was the 800MB limit introduced?
,
Oct 12
|
||||
►
Sign in to add a comment |
||||
Comment 1 by l...@chromium.org
, Nov 2 2017