This bug was filed from the Socorro interface and is report bp-8013830a-b30f-4eee-a1d4-902e12140710. ============================================================= STR: disabled D2D,OMTC user_pref("gfx.direct2d.disabled", true); user_pref("layers.offmainthreadcomposition.enabled", false); The first bad revision is mozilla-inbound changeset 0a63018c83a5 Jonathan Watt — Bug 1034404 - Get rid of the Thebes backed gfxContexts in ThebesLayerD3D9. r=Bas about:support Graphics Adapter Description Mobile Intel(R) 4 Series Express Chipset Family Adapter Drivers igdumdx32 igd10umd32 Adapter RAM Unknown ClearType Parameters Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 100 Device ID 0x2a42 DirectWrite Enabled false (6.2.9200.16571) Driver Date 10-13-2011 Driver Version 8.15.10.2555 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 9 Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Mobile Intel(R) 4 Series Express Chipset Family Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote false AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0

Bas, do we care about supporting this combination?

Isn't that combo true/valid for all D2D blacklisted GPUs up to release (where OMTC is disabled as of yet)? If Bug 1036457 get's "fixed" this should be WFM.

(In reply to XtC4UaLL [:xtc4uall] from comment #2) > Isn't that combo true/valid for all D2D blacklisted GPUs up to release > (where OMTC is disabled as of yet)? If Bug 1036457 get's "fixed" this should > be WFM. OMTC is never disabled on windows these days, or at least not if things are working right.

A French user reported this bug, is there something on his side he could do? http://forums.mozfr.org/viewtopic.php?f=5&t=121593

His about:support: Date du pilote 3-6-2011 Date du pilote (GPU 2) 11-12-2014 Description de la carte Intel(R) HD Graphics Family Description de la carte (GPU 2) NVIDIA GeForce GT 550M DirectWrite activé false (6.2.9200.16571) Fenêtres avec accélération graphique 0/1 Basic GPU 2 actif false ID du périphérique 0x0116 ID du périphérique (GPU 2) 0x0dd6 ID du sous-système 04b81028 ID du sous-système (GPU 2) 04b81028 ID du vendeur 0x8086 ID du vendeur (GPU 2) 0x10de Pilote de la carte (GPU 2) nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Pilotes de la carte igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 igd10umd32 RAM de la carte Unknown RAM de la carte (GPU 2) 1024 Rendu WebGL Google Inc. -- ANGLE (Intel(R) HD Graphics Family Direct3D9Ex vs_3_0 ps_3_0) Version du pilote 8.15.10.2321 Version du pilote (GPU 2) 9.18.13.4475 windowLayerManagerRemote false AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0

(In reply to Loic from comment #4) > A French user reported this bug, is there something on his side he could do? > http://forums.mozfr.org/viewtopic.php?f=5&t=121593 if he switched off D2D (gfx.direct2d.disabled) and OMTC (layers.offmainthreadcomposition.enabled) he want to switch off `layers.acceleration.disabled` too. unfortunately it's impossible to change this in about:config because firefox keeps crashing at start up. btw he can change it through prefs.js[1] file by adding: user_pref("layers.acceleration.disabled", true); [1] https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data#w_finding-your-profile-without-opening-firefox

Hi, I just bumped into this issue. I haven't disabled neither gfx.direct2d.disabled nor layers.acceleration.disabled just OMTC but FF still crashes in the first 2 or 3 seconds after startup. This flag was pointed out as a cure for the "freezing on tab close/switch" issue. Here is the bug report: https://crash-stats.mozilla.com/report/index/9600e815-8e41-4f6e-8a6a-4c22e2150210

gfx.direct2d.disabled == false layers.offmainthreadcomposition.enabled == false (because of https://bugzilla.mozilla.org/show_bug.cgi?id=1065463) Got two crashes in row: https://crash-stats.mozilla.com/report/index/a65a82a8-a2b9-4e96-8fa0-5449c2150218 https://crash-stats.mozilla.com/report/index/eec10d99-696b-4085-89e9-06d542150218

Firefox crashes again and again on YouTube. Looks like Google started to force HTML5 video today.

Are you seeing the same problems on Beta?

(In reply to Milan Sreckovic [:milan] from comment #10) > Are you seeing the same problems on Beta? Yes bp-78d4f552-ac17-4d3f-976d-95ba72150220 and aurora bp-c03046f1-14cf-4e2a-b97c-dee482150220 I think it fixed in Nightly.

Using STR in comment 0: Last crash: mozilla-central changeset 34e2d2bd7ec4 (Nightly 2015-01-22-03-02-02) No longer crash since mozilla-central changeset a6bbabebed2f (Nightly 2015-01-23-09-33-02) I'm going to close this as fixed.