can you take some memory-infra traces? instructions here: https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs#TOC-Capture-a-trace-from-Chrome-on-Android-with-DevTools-

Make sure to manually select trace categroies and make sure "memory-infra" is selected.

I think if this takes minutes to see the leak, then there probably isn't enough buffer space to record the whole thing. Maybe take a trace at the beginning of the process of maybe 10s, then take another one at the end. Make sure the same tabs are open in both traces, so can compare how memory has changed.

also is this only reproducible on that one device, or that's the only device you've tested?

Removing the WebView component, because the bug clearly states this happens in Chrome.

This component is only for WebView-specific bugs.

Adding Needs-feedback for the questions boliu@ posted.

I have the same issue on the same type of phone.
Sony Xperia Z3 Compact D5803
Android 6.0.1
Kernel 3.4.0-perf-gc14c2d5
Build number 23.5.A.1.291

The phone was constantly killing background apps and always acting like it was low on memory. The keyboard would be sluggish, the launcher would always get killed and restart, etc. Uninstalling Chrome (reverting back to 50.0 which is built into the phone) has resolved all of this and the phone feels like new. I was on chrome 59. 

I've attempted to record a trace, but not sure what demonstrates the leak in the trace. Do i need any other categories besides memory-infra? Will any personally identifiable information be included in the trace?

Sorry for my late reply.

To #3: I have only tested this one device.

Before I originally reported this issue, I could reproduce the issue several times. Every time I waited 1-2 days before I switched Chrome versions, because the memory usage goes up and down all the time and it takes a while until the memory gets really full.
Chrome 59 -> Memory issue
back to 50 -> No issue
again 59 -> Issue
back to 50 -> No issue
60 beta -> Issue
back to 50 -> No issue
...

After I posted this issue, I had a closer look using adb shell dumpsys meminfo and procstats when the memory was nearly full with Chrome 59 installed. Meminfo showed a huge amount of "Lost RAM", which looks a bit strange to me (see attached meminfo.txt). Unfortunately I only found out about /sys/kernel/debug/ion after I already rebooted the phone. :-( Maybe otherwise I could have seen something interesting...

To make things even more complicated:
After a further switch to 50 and then back to 59, I tried to reproduce it again to check /sys/kernel/debug/ion. But now the phone runs Chrome 59 without any memory issues for at least a week! I have no idea what is causing this.

If I see the memory issue again, I will check the ION debug entries.
I have no idea how I could record useful memory traces without opening and closing tabs, since it takes hours or days to reproduce the issue...

Deleted: meminfo.txt 11.5 KB

meminfo.txt 11.5 KB View Download

Thank you for providing more feedback. Adding requester "ntfschr@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I've been running Chrome 50.0 for several days and still having memory problems so I don't feel like I can fairly point at Chrome 59 anymore (or Chrome at all for that matter)

***Bulk edit***

Closing due to inactivity, please feel free to reopen if needed.