Profile: https://perfht.ml/2UpoG7b If remote debugging is enabled, then we spend 140ms on startup in `onEnable` in `GeckoViewRemoteDebugger.jsm`. This is not a default configuration, so it's not overly concerning, but it would be very nice to speed this up. At the moment, when profiling startup, I always need to turn off remote debugging, quit the app, launch it with startup profiling, re-enable remote debugging, and grab a profile. This is the only way to get realistic profiles without the devtools code, and it's a bit cumbersome. For reference, here are the first 3.5 seconds of startup with and without remote debugging enabled. Without remote debugging: https://perfht.ml/397wH6n With remote debugging: https://perfht.ml/3a84PQM
Bug 1623925 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Profile: https://perfht.ml/2UpoG7b If remote debugging is enabled, we spend 140ms on startup in `onEnable` in `GeckoViewRemoteDebugger.jsm`. This is not a default configuration, so it's not overly concerning, but it would be very nice to speed this up. At the moment, when profiling startup, I always need to turn off remote debugging, quit the app, launch it with startup profiling, re-enable remote debugging, and grab a profile. This is the only way to get realistic profiles without the devtools code, and it's a bit cumbersome. For reference, here are the first 3.5 seconds of startup with and without remote debugging enabled. Without remote debugging: https://perfht.ml/397wH6n With remote debugging: https://perfht.ml/3a84PQM