We ran a chrome browser for multiple days with memory-infra/native-heap-profiling and collected memory dumps periodically. These memory dumps were used to determine objects remaining (allocated, but not freed) and they are potential memory leak.

   blink::KeyframeEffectModelBase::EnsureInterpolationEffectPopulated() const

The stackframe attached to the bug can be observed on a gmail tab open for a week.

There is about ~40k object per tab. This was observed on different tab.
 

Deleted: bug1.png 107 KB

	bug1.png 107 KB View Download

Deleted: bug2.png 108 KB

	bug2.png 108 KB View Download

Deleted: bug3.png 103 KB

	bug3.png 103 KB View Download