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::InvalidatableInterpolation::EnsureValidConversion

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


 

Deleted: bug1.png 103 KB

	bug1.png 103 KB View Download

Deleted: bug2.png 102 KB

	bug2.png 102 KB View Download

Deleted: bug3.png 104 KB

	bug3.png 104 KB View Download

Deleted: bug4.png 105 KB

	bug4.png 105 KB View Download