Firefox Save And Quit
This is available starting with Firefox 52.This is the best and easiest way to do HTTP logging. At any point during while your browser is running, you can turn logging on and off. This allows you to capture only the 'interesting' part of the browser's behavior (i.e.
Firefox Quit Unexpectedly
Your bug), which makes the HTTP log much smaller and easier to analyze. Launch the browser and get it into whatever state you need to be in just before your bug occurs. Open a new tab and type in 'about:networking' into the URL bar.
Go to the 'Logging section'. Adjust the location of the log file if you don't like the default. Adjust the list of modules that you want to log: this list has the exact same format as the MOZLOG environment variable (see below). Generally the default list is OK, unless a Mozilla developer has told you to modify it. Click on Start Logging.
Reproduce the bug (i.e. Go to the web site that is broken for you and make the bug happen in the browser).
Make a note of the value of 'Current Log File'. Click on Stop Logging. Go to the folder containing the specified log file, and gather all the log files. You will see several files that look like: log.txt-main.1806, log.txt-child.1954, log.txt-child.1970, etc. This is because Firefox now uses multiple processes, and each process gets its own log file. For many bugs, the 'log.txt-main' file is the only thing you need to upload as a file attachment to your Bugzilla bug (this is assuming you're logging to help a mozilla developer). Other bugs may require all the logs to be uploaded-ask the developer if you're not sure.
Pat yourself on the back-a job well done! Thanks for helping us debug Firefox.Logging HTTP activity by manually setting environment variablesSometimes the about:networking approach won't work, for instance if your bug occurs during startup, or you're running on mobile, etc. In that case you can set environment variables.before. you launch Firefox. Note that this approach winds up logging the whole browser history, so files can get rather large (they compress well:)Setting environment variables differs by operating system. Don't let the scary-looking command line stuff frighten you off; it's not hard at all!
Windows. If Firefox is already running, exit out of it. Open a command prompt. On, you can find the 'Run.' Command in the Start menu's 'All Programs' submenu. On, you can hold down the Windows key and press 'R'.
Type CMD and press enter, a new Command Prompt window with a black background will appear. Copy and paste the following lines one at a time into the Command Prompt window. Press the enter key after each one.:For 64-bit Windows: set MOZLOG=timestamp,rotate:200,nsHttp:5,cache2:5,nsSocketTransport:5,nsHostResolver:5set MOZLOGFILE=%TEMP%log.txt'c:Program FilesMozilla Firefoxfirefox.exe'For 32-bit Windows: set MOZLOG=timestamp,rotate:200,nsHttp:5,cache2:5,nsSocketTransport:5,nsHostResolver:5set MOZLOGFILE=%TEMP%log.txt'c:Program Files (x86)Mozilla Firefoxfirefox.exe'(These instructions assume that you installed Firefox to the default location, and that drive C: is your Windows startup disk. Make the appropriate adjustments if those aren't the case.). Reproduce whatever problem it is that you're having. Once you've reproduced the problem, exit Firefox and look for the generated log files in your temporary directory. You can type '%TEMP%' directly into the Windows Explorer location bar to get there quickly.LinuxThis section offers information on how to capture HTTP logs for Firefox running on Linux.
Quit out of Firefox if it's running. Open a new shell. The commands listed here assume a bash-compatible shell. Copy and paste the following commands into the shell one at a time. Make sure to hit enter after each line.export MOZLOG=timestamp,rotate:200,nsHttp:5,cache2:5,nsSocketTransport:5,nsHostResolver:5export MOZLOGFILE=/tmp/log.txtcd /path/to/firefox./firefox. Reproduce the problem you're debugging.
When the problem has been reproduced, exit Firefox and look for the generated log files, which you can find at /tmp/log.txt.Mac OS XThese instructions show how to log HTTP traffic in Firefox on Mac OS X. Quit Firefox is if it's currently running, by using the Quit option in the File menu. Note: The generated log file uses Unix-style line endings. Older editors may have problems with this, but if you're using an even reasonably modern Mac OS X application to view the log, you won't have any problems. Start logging using command line argumentsSince Firefox 61 it's possible to start logging in a bit simpler way than setting environemnt variables: using command line arguments. Here is an example for the Windows platform, on other platforms we accept the same form of the arguments:.
If Firefox is already running, exit out of it. Open a command prompt.
On, you can find the 'Run.' Command in the Start menu's 'All Programs' submenu. Def environment(.env'MOZLOG' = 'nsHttp:5'return env See also. There are similar options available to debug mailnews protocols. See for more info about mailnews troubleshooting.
Firefox 63 Save And Quit Missing
On the Windows platform, nightly Firefox builds have FTP logging built-in (don't ask why this is only the case for Windows!). To enable FTP logging, just set MOZLOG=nsFtp:5 (in older versions of Mozilla, you need to use nsFTPProtocol instead of nsFtp). When Mozilla's built-in logging capabilities aren't good enough, and you need a full-fledged packet tracing tool, two free products are. They are available for Windows and most flavors of UNIX (including Linux and Mac OS X), are rock solid, and offer enough features to help uncover any Mozilla networking problem.
I understand that in earlier Firefox versions (I have seen this feature in Firefox 3 and 4, I don't know when it was removed, or hidden) there was an option in the dialog which asks you if you are sure you want to close the browser which would allow you to Quit & Save.This option would do almost the same thing as force quitting the browser currently does when it crashes or is unresponsive. Is there such an option in Firefox 50? I am running Ubuntu GNOME 16.10 with GNOME 3.22.I would like there to be an easy way of me accessing this option, however I won't want to use it too often due to security reasons so I don't want it to become the default.