Closed Bug 889702 Opened 11 years ago Closed 11 years ago
Crash on startup when running -metrodesktop
On current m-c, the app opens, throws "Assertion failure: aImage.type() == SurfaceDescriptor::TShmem, at /path/to/gfx/layers/d3d11/TextureD3D11.cpp:302" then crashes, even when ignored. This does not happen when OMTC is explicitly disabled in the app with: pref("layers.offmainthreadcomposition.enabled", false); As discussed with bbondy on IRC, we should disable OMTC automatically when running the app under -metrodesktop mode.
Can you provide a crash ID from about:crashes?
Whiteboard: [metro-crash][startupcrash] → [metro-crash][startupcrash] feature=defect c=graphic_display_features u=metro_firefox_user p=0
This doesn't block any release. The work around is to disable omtc.
No longer blocks: metrov1defect&change
related - bug 756606
See Also: → 756606
Summary: Defect - Crash on startup when running -metrodesktop → Crash on startup when running -metrodesktop
Whiteboard: [metro-crash][startupcrash] feature=defect c=graphic_display_features u=metro_firefox_user p=0 → [metro-crash][startupcrash]
Hm. I can't replicate this anymore on a more recent m-c build. And I can't seem to find anything under about:crashes on the machine that this cropped up on (presumably because I cleared the profile when testing something).
(In reply to Jonathan Wilde [:jwilde] from comment #4) > Hm. I can't replicate this anymore on a more recent m-c build. Closing as workforme for now. > presumably because I cleared the profile when testing something. Deleting your profile doesn't delete your crash IDs that are in another folder: %APPDATA%\Mozilla\Firefox\Crash Reports\submitted
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.