|
|
| Line 325: |
Line 325: |
|
| |
|
| To turn off debug output for the CEH, change the registry value from 01 to 00, or delete the CEHDump key. | | To turn off debug output for the CEH, change the registry value from 01 to 00, or delete the CEHDump key. |
|
| |
| === Diagnosing Startup Problems ===
| |
|
| |
| Due to the embedded nature of metro browsers, diagnosing startup problems can be a bit of a pain. There are a few things you can do to help devs figure out what's going wrong.
| |
|
| |
| <b>
| |
| 1) Launch the metro browser interface on desktop to confirm the install is working.
| |
| </b>
| |
|
| |
| * Navigate to firefox's install location in explorer
| |
| * Hold shift, right-click the folder with firefox.exe and select open command prompt.
| |
| * in the prompt type 'firefox.exe -metrodesktop'
| |
|
| |
| The metro front end should launch in a window on the desktop. If not, try uninstalling and re-installing. If that doesn't help, please file a bug.
| |
|
| |
| <b>
| |
| 2) Check Direct3D start up check results
| |
| </b>
| |
|
| |
| Using regedit.exe, check under the following key for a value named 'MetroD3DAvailable':
| |
|
| |
| HKEY_CURRENT_USER\SOFTWARE\Mozilla\Firefox
| |
|
| |
| If the value is 0, Direct3D startup checks failed. Please file a bug, and post the Graphics section of your desktop browser's about:support section to the bug. If there is no value, please file a bug. If the value is 1, startup checks succeeded.
| |
|
| |
| <b>
| |
| 3) Check for submitted crashes reports
| |
| </b>
| |
|
| |
| To check if metro fx is generating and submitting crash reports open explorer to the following path:
| |
|
| |
| C:\Users\(youraccount)\AppData\Roaming\Mozilla\MetroFirefox\Crash Reports\submitted\
| |
|
| |
| If the folder exists and contains text files please file a bug and copy the contents of a few of the most recent files into the bug.
| |
|
| |
| <b>
| |
| 4) Check for unsubmitted crashes reports
| |
| </b>
| |
|
| |
| Metro firefox can not submit crashes for analysis unless the browser fully starts ({{bug|797023}}).
| |
|
| |
| To check if metro fx is crashing on startup, open explorer to the following path:
| |
|
| |
| C:\Users\(youraccount)\AppData\Roaming\Mozilla\MetroFirefox\Crash Reports\
| |
|
| |
| In this folder look for two files:
| |
|
| |
| LastCrash lastCrashFilename
| |
|
| |
| If both files are present, delete them, and try restarting Metro Firefox again. After doing this, check the folder again. If the files return, a startup crash is likely.
| |
|
| |
| There are two things you can do t this point to help diagnose the problem:
| |
|
| |
| <b>Option 1</b>: Use Desktop Firefox to submit the crash report to Mozilla's crash server -
| |
|
| |
| * open lastCrashFilename with notepad.exe
| |
| * copy the temp path and note the file name of the crash report
| |
| * open the temp path in explorer and locate the two files associated with the report.
| |
|
| |
| There will be two files, both will have the same file name (a uuid string) and the extensions .dmp and .extra.
| |
|
| |
| * shutdown desktop firefox if it is running
| |
| * In explorer, copy both files from their location into the follow folder:
| |
|
| |
| C:\Users\(youraccount)\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending\
| |
|
| |
| * start Desktop Firefox.
| |
| * Navigate to 'about:crashes'.
| |
| * find the uuid of the report you copied and click on its link
| |
|
| |
| If the link does not resolve to a crash server crash report immediately, wait a few minutes and try again. Once the link resolves, file a bug and copy the report's link into the bug report.
| |
|
| |
| <b>Option 2</b>:
| |
|
| |
| File a bug and contact a dev. who you can share your crash report with. Note crash reports can contain user specific info, do not submit these files to bugzilla as attachments.
| |
|
| |
| <b>
| |
| 4) Logging startup
| |
| </b>
| |
|
| |
| ..
| |
|
| |
| <b>
| |
| 5) CEH logging
| |
| </b>
| |
|
| |
| ..
| |
|
| |
|
| == Testing Harness == | | == Testing Harness == |