[0]: https://wiki.mozilla.org/Performance/Snappy [1]: https://wiki.mozilla.org/Performance/MemShrink [2]: http://blog.kylehuey.com/post/21892343371/fixing-the-memory-...
There's a lot of work still to be done, but those pauses should go away over time.
(It's me from freenode :b )
I haven't recreated my profile in a while, possibly time to give that a go.
A quick verification can be to start Firefox with the -profilemanager flag and create a new profile, and verify if it does or does not occur in a completely fresh profile.
In my case, pauses came from FoxyProxy regular expression pattern matching on urls where I was using:
(.*\.)*
to match subdomains. The issue went away when I did: (?:.*\.)?
instead - non-capture, and of course noticing that . matched \. too.Their idea is that it is an HTML5 standard with some additional Javascript hooks for hardware access, so any browser could be the 'core' with only a few tweaks.
This mostly applies to the Marketplace in how it offers paid apps; we have a decentralized receipt format to let the paid app run on any platform. Unlike any other mobile player, Mozilla is truly making the web the platform. Our platform is not Firefox OS. That's just one device to support open web apps.
"Gecko on top of it. The same version you'll find on a regular Firefox;"
Maybe we're confusing web standards with rendering engines, but this is a product with only one rendering engine.
I don't know if this has been fixed. But anyways, I won't go back to Firefox.