touch-packages team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

Marcos, I just had a quick look at the code for unav, and I think it
would be very useful if you could 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.

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


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?
Also, I’m not really sure what purpose the "if (prev_run <= $.now())" test serves. According to the W3C spec for watchPosition (http://dev.w3.org/geo/api/spec-source.html#watch-position): « the successCallback is only invoked when a new position is obtained and this position differs significantly from the previously reported position ». So presumably if you get two success callbacks in a row, it’s because the position has changed enough that you really want to update the position on the map anyway.

** Also affects: oxide
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1462664

Title:
  Geolocation app is freezing in a few mobiles

Status in Oxide Webview:
  New
Status in uNAV:
  Confirmed

Bug description:
  Hi!

  With the app GPS Navigation a few users have problem with a freeze
  issue, because of 100% CPU usage or heavy swap usage (I don't know,
  because I can't reproduce it.

  For some users, it is working perfect, for other is freezing after a few minutes. You can see here the user reviews:
  https://uappexplorer.com/app/navigator.costales

  The code is here:
  http://bazaar.launchpad.net/~costales/unav/trunk/view/head:/www/js/geolocation.js
  It's just a simple HTML5 geolocation code. Even I added a reject control for more that 1 request by 800 microseconds.

  I think it could be the GPS doing a lot of request by second or the
  web container is freezing waiting for GPS.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1462664/+subscriptions