From 5e6e3c9be9ad59485bb5fcb4b3f474a1f0ea77e0 Mon Sep 17 00:00:00 2001 From: Roman-Nopantski Date: Fri, 24 Feb 2017 05:05:34 +1300 Subject: [PATCH] Created Troubleshooting (markdown) --- Troubleshooting.md | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 Troubleshooting.md diff --git a/Troubleshooting.md b/Troubleshooting.md new file mode 100644 index 0000000..26bd8c4 --- /dev/null +++ b/Troubleshooting.md @@ -0,0 +1,34 @@ +## How to troubleshoot a preference + +1. Download and unpack a portable Firefox + * Current stable Firefox portable is [here](http://portableapps.com/apps/internet/firefox_portable) + * Older versions are [here](https://sourceforge.net/projects/portableapps/files/Mozilla%20Firefox%2C%20Portable%20Ed./) +2. Create a profile and test the problem + * Open Firefox and go to the web page where you can replicate the problem and bookmark it + * Verify that the problem does not exist in a vanilla Firefox setup. +3. Set up a profile-master for quick resets + * Go to the `\FirefoxPortable\Data\profile` folder and create an empty user.js file + * Then go up a directory to the `\FirefoxPortable\Data\` folder and COPY the `profile` folder. Rename it `profile-master` (we can use this to quickly restore to a vanilla profile) +4. Make sure the user.js is the cause + * Replace the user.js in your `profile` folder with the full user.js. + * Restart Firefox and confirm the problem exists +5. Reset the profile folder + * Close Firefox + * Go to the `\FirefoxPortable\Data\` folder and delete the `profile` folder. + * COPY the `profile-master` folder and rename it `profile` +6. Addition method (do step 6 or 7) + * In your `profile` user.js (which initially should be empty), paste in the section (or sections) you suspect might be the culprit, save the changes and restart Firefox. + * Test if the problem exists. If not repeat the above step until you find it. +7. Halving method (do step 6 or 7) + * This method involves re-setting your vanilla profile often (see step 5) + * Use this method if you have no idea what section could be the cause. By testing half and then based on the results, testing the next quarter, and then based on those results testing the next eighth etc, you can rapidly narrow it down in four or five steps at most. + * With a preset profile (see step 5), edit the user.js and paste in half the sections eg 0100-1400, and save the changes. Restart Firefox and test if the problem exists. If it does we now know it is the 0100-1400 half that contains the culprit. If not, we know it is the 1600-3000 half. For this example the problem didn't occur. + * In a reset profile, edit the user.js and paste in half the 1600-3200 sections, eg 1600-2500, and save the changes. Restart Firefox and test if the problem exists. If it does we now know it is the 1600-2500 half that contains the culprit. If not, we know it is the 2600-3000 section. + * Keep repeating these steps to narrow it down + * You can also use this method to halve big sections such as 2600 +8. Checking preference by preference + * In a reset profile (see step 5), paste in the offending section (or sections) into the user.js and save the changes. Restart Firefox. + * Go to about:config, find the first preference and right click and reset it. Test if the problem exists. + * If the problem still exists, clear your cache and repeat the above step + +The End