Can anybody advise on how I can "reclaim" ram when using
webview to display many screens of locally-stored html.
It is as though memory for webviews is never released until the app is killed.
Each webview screen typically contains text and 1 jpeg of around 50K.
Speed of displaying screens and of scrolling becomes progressively slower
as more pages are viewed. After 85 webviews, scrolling becomes unusable.
Screen display time is still tolerable, but gradually slowing.
I used task manager to monitor ram usage:
On initial loading it is 7.8mb. After displaying 4 webview screens it is 10.72mb
This rises to 17mb after 36 "webviews" and to 28mb after 85 webviews.
If I go backwards/forwards displaying the same screen repeatedly, ram usage continues to rise.
My app has 300 jpegs (10mb of storage).
My apk is around 10mb
webview to display many screens of locally-stored html.
It is as though memory for webviews is never released until the app is killed.
Each webview screen typically contains text and 1 jpeg of around 50K.
Speed of displaying screens and of scrolling becomes progressively slower
as more pages are viewed. After 85 webviews, scrolling becomes unusable.
Screen display time is still tolerable, but gradually slowing.
I used task manager to monitor ram usage:
On initial loading it is 7.8mb. After displaying 4 webview screens it is 10.72mb
This rises to 17mb after 36 "webviews" and to 28mb after 85 webviews.
If I go backwards/forwards displaying the same screen repeatedly, ram usage continues to rise.
My app has 300 jpegs (10mb of storage).
My apk is around 10mb