Closed Bug 971301 Opened 7 years ago Closed 5 months ago
Investigate console logging expenses
Nick and I have a sneaking suspicion that calls to Log.* and isLoggable are having an impact on our overall perf. It is, after all, I/O -- and a lot of it. And a lot of string concatenation, allocation, and GC, too. We should: * Measure * Switch to Logger (which is more efficient) or remove log statements * Consider the use of selective preprocessing or Proguarding to eliminate the argument-compilation costs of disabled logging. Furthermore, I think that initializing for a console.log statement in browser.js is causing ConsoleAPI.init to have a measurable impact on our startup profile. This is called from HealthReportStatusListener.init() @ browser.js:5529 pbu_privacyContextFromWindow() @ PrivateBrowsingUtils.jsm:23 AppUtils.jsm (via Webapps*) We should strip out unnecessary logging from browser.js and its dependent modules so that we can delay initialization of the console API.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.