I've seen it use up to 80MB USS. That's pretty crazy. It results in all other background apps being killed off, reliably. I took a peek at an about:memory dump and saw that the maps app is using 20 Worker threads. Those aren't cheap. Easiest win would be reducing the number of workers. Donovan, can you talk to our contacts about this?

Yep. I already mentioned it to them. I'll mention it again.

It seems to behave a fair bit better now, I tried running it for a while in both map and satellite mode and it seems to peak at around ~50 MiB, when sent to the background it drops to less than 30 MiB.

I don't think anything has changed in the maps code. It's still using a ton of worker threads etc. I think gecko is dealing with it better.

We should be using only one worker at a time. We will investigate if this was not corrected properly.

Guys, we corrected this in Dec. 2012. Could you please retest whether we still have multiple workers?

We corrected this in Dec. 2012 @Nokia. Could you please retest whether we still have multiple workers?

(In reply to AndyT from comment #6) > We corrected this in Dec. 2012 @Nokia. Could you please retest whether we > still have multiple workers? I think this was fixed when we moved to a packaged app. Closing this as such.