> are you sure the renderer is killed in executeJavaScript(…) ?
I don't know where.
> circumstances the page becomes blank (in the bug report)?
I think when the app returns to foreground the system kills the rendered,
but I can't confirm that.
I saw this behavior in other apps (specially in previous OTAs), but in uNav
(I think) it is because it has an heavy use of CPU & RAM.
> Have you tried monitoring the value of webProcessStatus¹ on the webview?
Hi Olivier :)
> are you sure the renderer is killed in executeJavaScri pt(…) ?
I don't know where.
> circumstances the page becomes blank (in the bug report)?
I think when the app returns to foreground the system kills the rendered,
but I can't confirm that.
I saw this behavior in other apps (specially in previous OTAs), but in uNav
(I think) it is because it has an heavy use of CPU & RAM.
> Have you tried monitoring the value of webProcessStatus¹ on the webview?
No, I added this dump now (revision 136 bazaar. launchpad. net/~costales/ unav/0. 64-webview- empty-then- reload/ revision/ 136>,
<http://
If
you see it is wrong, please, ping me):
webview.
> probably be useful to keep the error code and explanation
I restored them. Anyway, they are always like in my log in ubuntu pastebin.
I'll test it these weeks, with the new webProcessStatus and check if the
reload it's working in all cases.
Thanks Olivier!