Comment 10 for bug 1462664

Hi Olivier! Thanks a lot for your support! Really :)

> instrument the JS code with a few debug logs to try and figure out what’s
going on for users who can observe the freeze.

I'll do it ;) but will be this a problem with a big .log for the system?
the app will write several lines every second.

> Could you get someone who can reliably reproduce the issue attach the
corresponding log file? It should be at
/home/phablet/.cache/upstart/application-click-navigator.costales_navigator_0.11.log

This is the log without the debug trace: http://paste.ubuntu.com/11696576/
I didn't see anything on it.

> Is it possible that the index.html page is ever reloaded, thus leading to
more than one call to watchPosition() through the lifetime of the app?

I think not.

> Also, I’m not really sure what purpose the "if (prev_run <= $.now())"
test serves

Yes, I'm agree with you, but for example, I'm getting 1 position for every
~600 microseconds. As so many users reported a freeze problem, I'm forcing
just 1 call in 800 microseconds. But the users have the same problem.

> it’s because the position has changed enough that you really want to
update the position on the map anyway

It's giving me a problem, because between position & position I'm
calculating things like rotation, distance, time, I'm on route, draw the
map...
Then, the app has problem with a big (really big) routes (Madrid-Berlin for
example).

A hug!