> @Marcos: what do you mean by "uNav is generating a lot of
> process/second"?
uNav is doing a lot of calculations by second when you're driving.
Then the CPU usage is so high.
> IIRC I once suggested you to monitor the 'webProcessStatus' property of
> the webview, and offer some user feedback when it’s killed or crashed.
We have this log from users and experimented by myself:
file:///opt/click.ubuntu.com/navigator.costales/0.59/qml/Main.qml:103:
TypeError: Type error
ubuntumirclient: Attempted to deliver an event to a non-existent
window, ignoring.
This is because the webview was killed and uNav doesn't find it.
Regenerate the webview could be a solution, but it would lost a current route.
Hi Olivier :)
> @Marcos: what do you mean by "uNav is generating a lot of
> process/second"?
uNav is doing a lot of calculations by second when you're driving.
Then the CPU usage is so high.
> IIRC I once suggested you to monitor the 'webProcessStatus' property of
> the webview, and offer some user feedback when it’s killed or crashed.
We have this log from users and experimented by myself:
file:// /opt/click. ubuntu. com/navigator. costales/ 0.59/qml/ Main.qml: 103:
TypeError: Type error
ubuntumirclient: Attempted to deliver an event to a non-existent
window, ignoring.
This is because the webview was killed and uNav doesn't find it.
Regenerate the webview could be a solution, but it would lost a current route.
A hug!