Issue metadata
Sign in to add a comment
|
[Chrome][M51][Android 6.0.1] Can't load more that 20 tabs
Reported by
seiyon.p...@gmail.com,
Jul 18 2016
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Precondition : free space of RAM is very low 2. Launch Chrome 3. Touch "Overflow menu" 4. Touch "New tab" and open the site 5. Repeat touching "Overflow menu", "New tab" and opening another site until can't load new tab properly. What is the expected behavior? User can open the site properly when loading new tab. What went wrong? User can't open the site properly when loading new tab. Did this work before? N/A Chrome version: 51.0.2704.81 Channel: stable OS Version: 6.0.1 Flash Version: Shockwave Flash 22.0 r0 I assumed that it is reproducible only when memory (RAM) is not enough to load new tab. But my assumption is not correct due to the test results on two devices. The free memory of D850ATT is 148260 kB.(Attachment : D850PR.txt) The free memory of K200 is 57692 kB. (Attachment : K200.txt) I can't load new tab any more on D850ATT but I can load new tab on K200 even if the free memory of D850ATT is bigger that K200.
,
Jul 21 2016
What do you mean you can't load a new tab properly? Does it not render correctly? Does it crash due to OOM?
,
Jul 29 2016
I've uploaded video file.
,
Jul 29 2016
,
Jul 29 2016
,
Jul 29 2016
,
Jul 29 2016
,
Aug 9 2016
Gentle reminder
,
Sep 7 2016
Reminiscent of issue 429657 .
,
Sep 19 2016
For high-end phones with 4GB of RAM, we've seen the background app limit set to 60 by the chipset vendor (i.e., ro.sys.fw.bg_apps_limit=60). In that scenario, all 20 sandbox services could be active without triggering a low-memory situation, and Chrome won't load more than 20 tabs.
,
Dec 8 2016
it is not OOM.the sanbox process count can't more than 20.some device has more memory like 6GB.So the sanbox process will not kill by oom protect.
,
Aug 24 2017
bauerb@ is this on the roadmap to be looked at, the issue has gone a little quiet
,
Aug 25 2017
Can you capture a bugreport or logcat dump from the device when that happens?
,
Aug 25 2017
Given that the reported version of this bug in M-51 and https://bugs.chromium.org/p/chromium/issues/detail?id=429657 was fixed in M-59, I am pretty sure it's just a duplicate of that.
,
Aug 25 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rsgav...@chromium.org
, Jul 21 2016Status: Assigned (was: Unconfirmed)