Missing instructions on how to log what Firefox is doing at startup
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
People
(Reporter: tschweikle, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4086.0 Safari/537.36
Steps to reproduce:
Tried ' "C:\Program Files\Mozilla Firefox\Firefox.exe" -console -verbose -debug '
Actual results:
Firefox started, but did not tell in any way what it was doing while starting.
Expected results:
Firefox shall provide a way of logging what it is doing at startup. from what is done from starting the application until waiting for input.
Or some of the webpages available shall give what hast to be done to get such a log.
|
Reporter | |
Comment 1•4 years ago
|
||
Had looked at MDN. Found various descriptions debugging all aspects of Firefox, but nothing about how to debug startup:
- Application initialisation
- reading configuration
- reading gpo configurations
- reading default application settings
Firefox does reset some settings: external applications to handle documents f.e. to defaults and I need to find out why. Seems impossible at the time being.
|
||
Comment 2•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Console' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 3•4 years ago
|
||
(not sure about the component, but doesn't seem DevTools related)
|
||
Comment 4•4 years ago
|
||
Firefox doesn't have a good logging story unfortunately. We have multiple logging systems, different components use different logging mechanisms to different extents. This is all complicated by the presence of multiple processes. Even if you turned on all the logging systems it is quite likely you still wouldn't see a full picture of what Firefox is doing on startup. Solving that is a large project that frankly I don't think is worth the time to complete.
For the specific cases you mention you're going to be better off either using debugging tools to step into the code to understand it or file more specific issues on logging for those cases.
Description
•