Build: Device - Unagi Date - 11/11/2012 Steps: 1. With a wifi connection, launch the maps app 2. Select route 3. Select a from and to location Expected: The phone's responsiveness should remain usable from a user's perspective, even if you leave the app. Actual: The phone's responsiveness goes down to a crawl. The first time I did this, I exited to the homescreen app in attempt to get out of the maps app slowness, and the homescreen didn't load for 20 seconds, then i just shutdown the phone entirely. On the second try, the phone eventually crashed entirely.

I'm guessing this could be a OOM crash I'm seeing.

Attached logcat, although in this logcat example, the crash of the whole phone didn't happen. The scenario this logcat shows is when I do the following: 1. Go to maps app 2. Do a route over 300+ miles 3. Hit homescreen 4. Re-launch maps app Result - You'll notice that the maps app must have been killed will no user notice at all in this scenario, as the maps app doesn't return back to where the user was at, it restarts entirely.

Here's another logcat for the case when the entire phone crashes.

Donovan, Chris, we need to bring this back to the developers of this app.

Ok, I'll mention it to them.

Setting priority based on triage discussions. Feel free to decrease priority if you disagree.

Profile gathered while browsing around in directions from LA --> NY http://people.mozilla.com/~bgirard/cleopatra/#report=5b1b554fb151c38af60c1be1baa808661583c540 During some of the really unresponsive times, we're spending a bunch of time under Traffic:_reloadIncidents(). This is happening off a touchend handler.

Thanks for profiling it, that's really useful info.

Been >2 weeks, any update here Donovan?

Nokia implemented a fix for this by simplifying the route they draw when zoomed out, and it may already be rolled out on the server by now.

Sounds like we should close this then.

I just tested on the phone, it was able to route from here to new york without crashing or becoming unusably slow.