App update status – week of 11/6
7 November 2009With the landing of Bug 311965 time spent during startup in app update on mobile devices should have improved by around 72%. On Firefox WinCE this equates to reducing the time spent during startup in app update from over 180ms to around 50ms. This is on top of a previous reduction of around 25% from over 200ms to around 150ms as measured on Maemo Fennec and with this latest change I estimate the time spent in startup on Maemo Fennec to be around 40ms.
Progress:
- Landed on trunk and 1.9.2 branch – Bug 311965 [Toolkit] – Refactor nsUpdateService.js to load less code at startup.
- Landed on 1.9.2 branch – Bug 522583 [Toolkit] – nsUpdateService.js.in cleanup (remove previous update migration code, defineLazyServiceGetter for nsIObserverService, and other cleanup).
- Landed on 1.9.2 branch – Bug 521452 [Toolkit] – nsUpdateService and nsBlocklistService both have getFile(key, pathArray). Had to backout the changes to nsExtensionManager.js.in due to Bug 526441 [Toolkit] – Unable to use FileUtils.jsm in nsExtensionManager.js.in on 1.9.2 due to reftest failures.
- Landed on 1.9.2 branch – Bug 521956 [Toolkit] – nsUpdateService, nsExtensionManager.js.in and, nsBlocklistService include badCertHandler.js
Future targets:
- Finish up several decent sized reviews in my queue I haven’t had time to do.
- Blog about the lessons I’ve learned while trying to improve startup time for app update.
- Investigate Bug 525390 [Toolkit] – 3.5.4 Upgrade failure: entry point js_SaveRegExpStatics could not be located
- Investigate Bug 526441 [Toolkit] – Unable to use FileUtils.jsm in nsExtensionManager.js.in on 1.9.2 due to reftest failures.
- I’m going to try to get Bug 407875 [Toolkit] – Unprivileged users are not notified of security updates fixed for Firefox 3.6.
No comments yet