User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.96 Safari/537.4 Steps to reproduce: 1/ I installed firefox latest ELM on a brand new Windows 8 x64, launched it, set it as default browser, launched Metro Firefox. => Crash 2/ I had a look at the MetroFirefox minidumps (see attached file), found an issue with gl layers ? gl layers-. 3/ Updated to the latest available drivers from Nvidia => Crash 4/ prefs.js was empty in Metrofirefox profile as it was not able to start at least once, so I copied prefs.js from Standard Firefox with gl layers disabled => Crash 5/ minidump again, D2D ? D2D- 6/ as in 4, with gl layers and D2D disabled => Crash and nothing useful in minidump .extra file to try to disable something else Actual results: Crash at startup, all the time Expected results: No crash

Were you using a VM for this? This sounds like a dupe of bug 797013.

I saw bug 797013 before filling this one but as I'm not in a VM I thought it could be a different one. I've tried all ELM builds of october, they all crash at startup. I don't know for older builds though.

I have checked the hardware on this computer, here is dxdiag output: Driver File Version: 9.18.0013.0697 (English) Driver Version: 9.18.13.697 DDI Version: 9Ex Feature Levels: 9.3,9.2,9.1 So it looks like it is definitely a DX10 problem as in bug 797013, so mine is a dupe and should be closed.

Fixing bug 797013 did not solve this one. MetroFireforx launches onces, but if I close and restart it it crashes with the same GLlayers- error as before, see below: AdapterVendorID=0x10de StartupTime=1352922844 EMCheckCompatibility=true ProductName=MetroFirefox Vendor=Mozilla InstallTime=1352922776 FramePoisonBase=00000000f0de0000 Theme=classic/1.0 Notes=AdapterVendorID: 0x10de, AdapterDeviceID: 0x029e, AdapterSubsysID: 032c10de, AdapterDriverVersion: 9.18.13.697\nD2D! D2D- WGL? GL Context? GL Context+ WGL+ GL Layers? GL Layers- FramePoisonSize=65536 Version=19.0a1 ReleaseChannel=nightly-elm ServerURL=https://crash-reports.mozilla.com/submit?id={99bceaaa-e3c6-48c1-b981-ef9b46b67d60}&version=19.0a1&buildid=20121114040203 AdapterDeviceID=0x029e Add-ons= BuildID=20121114040203 ProductID={99bceaaa-e3c6-48c1-b981-ef9b46b67d60} CrashTime=1352922845 SystemMemoryUsePercentage=51 TotalVirtualMemory=4294836224 AvailableVirtualMemory=4039659520 AvailablePageFile=3240792064 AvailablePhysicalMemory=1033084928 And here is prefs.js: user_pref("app.update.lastUpdateTime.addon-background-update-timer", 0); user_pref("app.update.lastUpdateTime.background-update-timer", 0); user_pref("app.update.lastUpdateTime.blocklist-background-update-timer", 0); user_pref("app.update.lastUpdateTime.search-engine-update-timer", 1352922798); user_pref("browser.startup.homepage_override.mstone", ""); user_pref("extensions.blocklist.pingCountVersion", 0); user_pref("extensions.bootstrappedAddons", "{}"); user_pref("extensions.lastAppVersion", "19.0a1"); user_pref("extensions.lastPlatformVersion", "19.0a1"); user_pref("extensions.shownSelectionUI", true); user_pref("formhelper.enabled", true); user_pref("gfx.direct3d.checkDX10", false); user_pref("pdfjs.migrationVersion", 1); user_pref("pdfjs.previousHandler.alwaysAskBeforeHandling", true); user_pref("pdfjs.previousHandler.preferredAction", 4); user_pref("places.history.expiration.transient_current_max_pages", 53643); user_pref("plugin.disable_full_page_plugin_for_types", "application/pdf"); user_pref("xpinstall.whitelist.add", ""); This happens with a clean install (user prefs deleted at uninstall) of latest elm from 12/11 and 14/11.

Can you provide the crash ID from about:crashes?

I have to delete the metrofirefox directory in order to be able to launch it again, so I guess about:crashes won't give me anything, right ?

Comment 4 doesn't give anything useful about the stack trace. The crash IDs are stored in %APPDATA%\Mozilla\Firefox\Crash Reports\submitted so if you don't delete this folder (different from the profile one) you will see them in any other Firefox.

I've made once again a clean install of latest elm from 14/11 and reproduced the bug. Unfortunately in about:crashes I get: Submitted Crash Reports No crash reports have been submitted. However I got .extra/.dmp minidump files in \Profiles\whatever.default\minidumps, is that enough for you ?

Some news. In prejs.js there is this line: user_pref("gfx.direct3d.checkDX10", false); If I switch it manually to true with notepad MetroFF starts again for one time again, then refuses to start once closed. Modifying it in about:config produces exactly the same behaviour, works once then crash. My GPU is not directX10 compliant.

Does it happen if you always start Firefox in Safe Mode (see https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)?

Clean install of latest elm 15/11 click on MetroFF tile while pressing the shift key -> crash Clean install again click on MetroFF NOT holding the shift key -> works once click on MetroFF NOT holding the shift key -> then crash click on MetroFF tile while pressing the shift key -> crash, crash, crash :) I can't find the equivalent of the Help menu of Standard Firefox in MetroFF so I CAN NOT test the following scenario Clean install click on MetroFF NOT holding the shift key -> works once Ask MetroFF to restart in safe mode I'll be afk for a few days, sorry.

(In reply to Ipmetro from comment #10) > Some news. > In prejs.js there is this line: > user_pref("gfx.direct3d.checkDX10", false); > > If I switch it manually to true with notepad MetroFF starts again for one > time again, then refuses to start once closed. > Modifying it in about:config produces exactly the same behaviour, works once > then crash. > > My GPU is not directX10 compliant. DirectX 10 is required to use Firefox for the modern UI. Eventually, attempting to launch Firefox for modern UI will simply launch desktop Firefox (see bug 807669) but for now it just crashes.

Well actually it does not "just crash", it works perfectly well once then it crashes if I attempt to launch it a second time, unless I delete prefs.js or switch gfx.direct3d.checkDX10 to True in prefs.js.