Hi,
Yeah, this is common problem with WebViews and regular desktop browsers really (Chrome, huh).
I don’t know how to fix it, although I am not sure if it’s really memory leak here.
Keep in mind that this memory is used by JavaScript engine which might release its state long time after you app get closed. It’s not handled by Android’s GC or reference counting system on iOS.
In addition, there are some methods to “clear” resources taken by WebView, and I am calling them once user closes browser but haven’t really noticed they actually do anything.
Sorry for not being super helpful, but this is simply ignored by Apple/Google engineers for years.