Chrome hangs/chokes when --per-site-instance tab process reaches around 2.6-2.7gb memory.
Reported by
acesk...@gmail.com,
Feb 12 2017
|
||
Issue descriptionSteps to reproduce the problem: 1.The chrome tab process chokes/hangs when it reaches around 2.6-2.7GB memory limit. Easiest way to approach the limit is to open memory heavy tabs with the same origin What is the expected behavior? I think chrome should create a new tab process when it nears the memory limit, and place remaining same origin tabs in the newly created process to prevent hitting the memory limit and choking. What went wrong? Chrome process-per-site chokes at 2.6-2.7GB memory limit per tab process. Did this work before? No Chrome version: 56.0.2924.87 Channel: stable OS Version: Windows 10 Flash Version:
,
Feb 15 2017
Considering this as a feature request. Marking it as untraiged.So that respective team would look into this. Thanks!
,
Feb 15 2017
I think this is a v8 limitation so ideally fixing the underlying cause should be best. But this could be a quick workaround without changing too much. |
||
►
Sign in to add a comment |
||
Comment 1 by ajha@chromium.org
, Feb 13 2017