We have a temporary fix in place that reverts the cold launch time and memory regressions caused around April 1st [1].
The root cause of the problem is that NUWA requires a stable state where all threads are idle during our boot process. We found that our current idle detection mechanism is very fragile and we need a better solution going forward. For example, [2] broke NUWA and caused a multiple second startup and multiple MB memory regression for every app. Please ping us if you can trigger similar regressions. We need to know the use-cases that can break NUWA and our pre-allocated process. -Gregor [1] http://raptor.mozilla.org [2] https://github.com/mozilla-b2g/gaia/pull/29900/files On Thursday, May 7, 2015 at 4:22:55 PM UTC+1, Gabriele Svelto wrote: > I've filed bug 1151672 [1] with full memory reports attached. I've CC'd > some people who might be interested but feel free to add more. It seems > that bug 1151672 [2] is responsible for most of the USS increase but > I've spotted some other issues outside of that, some of which look like > genuine regressions. > > Gabriele > > [1] Major memory usage regressions in v3.0 > https://bugzilla.mozilla.org/show_bug.cgi?id=1162535 > [2] Preallocated process approach not working on 2.2 and 3.0 > https://bugzilla.mozilla.org/show_bug.cgi?id=1151672 _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
