chrome://discards showing always zero discards on cyan |
||
Issue descriptionTitle says it all. The chrome://discard page shows 0 discards even after many discards have happened. Clicking on the "discard" link for a page does not increase the count. Actually, "always" is too strong. I just noticed that now it shows that 1 tab was discarded, the Calendar tab. OK now it's working... grrr. The chrome log is printing these frequently: 1415:1415:0316/113125.617879:WARNING:oom_memory_details.cc(46)] Tab Discards Memory details (2460 ms): followed by a tab list. But it's not clear what event is prompting these messages. So the situation is confusing.
,
Mar 27 2017
Raising priority because this is making it hard to debug current issues.
,
Mar 28 2017
This only happens when --enable-feature=MemoryCoordinator is specified. Is my understanding correct? I only changed tab discarding behavior when the flag is specified.
,
Mar 28 2017
#3 we noticed this problem before we were aware of the MemoryCoordinator feature, so this happened with whatever setting is the default (which I assume is ON).
,
Mar 28 2017
It's disabled by default but I'm running a finch experiment on Dev/Canary with 50% probability weight. Probably you were in the experiment group. I couldn't reproduce the issue though. "Discard" links are working on my ChromeOS device (regardless of memory coordinator is enabled/disabled).
,
Mar 28 2017
#5 thanks. As I should have mentioned, this behavior was observed on a ToT build. |
||
►
Sign in to add a comment |
||
Comment 1 by semenzato@chromium.org
, Mar 27 2017