[deploy preview] Export a tool to extract gecko logs from a profile
Open the Web console, enter extractGeckoLog().
After a while it should download automatically a txt file with the content of all logs. Note it doesn't take into account the range for now.
It is slow because running inside the web console runs the code only in the JS interpreter and never starts the JIT.
Fixes #4660
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 88.44%. Comparing base (
1507cdd) to head (a457ad3). Report is 17 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #4973 +/- ##
==========================================
+ Coverage 88.43% 88.44% +0.01%
==========================================
Files 304 304
Lines 27581 27607 +26
Branches 7458 7465 +7
==========================================
+ Hits 24390 24416 +26
Misses 2963 2963
Partials 228 228
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Hey @julienw -- this seems to work very well for me!
I've asked the necko folks to add feedback as well.
• The output didn't seem to be recognized by logan -- there might be a small export change required (this is a guess)
Current export: [Parent Process 158395 Socket Thread] D/nsSocketTransport engaging
But when I capture MOZ_LOG's natively: [Parent 87530: Socket Thread]: D/nsSocketTransport engaging
• Naturally a button or similar would be better than console commands :) • I didn't find the performance to be a problem at all.
I've looked at the output log and it looks great! Thank you.
Thanks all, I made the requested changes and added a test! I also tested after the changes that logan would be able to import the resulting file.
This should now be ready for review :-)
Used this again today, very nice ;)