Closed
Bug 960219
Opened 12 years ago
Closed 11 years ago
OMTC enabled results in low fps in Fish-GL demo.
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1000640
People
(Reporter: streetwolf52, Unassigned)
References
()
Details
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140115111138
Steps to reproduce:
1. Set 'layers.offmainthreadcomposition.enabled' = true
2. Run benchmark at http://www.unrealengine.com/html5/
Actual results:
FPS is 17. With OMTC set to false FPS is 60.
Expected results:
FPS should at least be 60 with OMTC set to true.
Reporter | ||
Comment 1•12 years ago
|
||
Graphics
--------
Adapter Description: AMD Radeon HD 7900 Series
Adapter Drivers: aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Adapter RAM: 3072
Device ID: 0x6798
Direct2D Enabled: true
DirectWrite Enabled: true (6.3.9600.16384)
Driver Date: 12-6-2013
Driver Version: 13.251.0.0
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Vendor ID: 0x1002
WebGL Renderer: Google Inc. -- ANGLE (AMD Radeon HD 7900 Series Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d
AzureContentBackend: direct2d
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0
Component: Untriaged → Graphics
Product: Firefox → Core
Comment 2•12 years ago
|
||
I'm also seeing this behavior.
Adapter Description AMD Radeon HD 7900 Series
Adapter Drivers aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Adapter RAM 3072
Device ID 0x679a
Direct2D Enabled true
DirectWrite Enabled true (6.2.9200.16581)
Driver Date 12-6-2013
Driver Version 13.251.0.0
GPU #2 Active false
GPU Accelerated Windows 1/1 Direct3D 11 (OMTC)
Vendor ID 0x1002
WebGL Renderer Google Inc. -- ANGLE (AMD Radeon HD 7900 Series Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote true
AzureCanvasBackend direct2d
AzureContentBackend direct2d
AzureFallbackCanvasBackend cairo
AzureSkiaAccelerated 0
Reporter | ||
Updated•12 years ago
|
Component: Graphics → Graphics: Layers
Reporter | ||
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•12 years ago
|
||
Confirmed with trunk build on Win7.
Adapter Description AMD Radeon HD 7700 Series
Adapter Drivers aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Adapter RAM 1024
ClearType Parameters Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 200
Device ID 0x683d
Direct2D Enabled true
DirectWrite Enabled true (6.2.9200.16571)
Driver Date 12-6-2013
Driver Version 13.251.0.0
GPU #2 Active false
GPU Accelerated Windows 1/1 Direct3D 11 (OMTC)
Vendor ID 0x1002
WebGL Renderer Google Inc. -- ANGLE (AMD Radeon HD 7700 Series Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote true
AzureCanvasBackend direct2d
AzureContentBackend direct2d
AzureFallbackCanvasBackend cairo
AzureSkiaAccelerated 0
Comment 4•11 years ago
|
||
URL is 404 now due to renewal of the site.
Reporter | ||
Comment 5•11 years ago
|
||
Same sort of problem with this demo: http://www.fishgl.com/
FPS cut in half when OMTC is turned on.
Reporter | ||
Updated•11 years ago
|
Summary: OMTC enabled results in poor Citadel demo/benchmark performance → OMTC enabled results in low fps in Fish-GL demo.
Comment 7•11 years ago
|
||
I think this can be closed since https://bugzilla.mozilla.org/show_bug.cgi?id=1000640 fixed the regression. Maybe, now another bug can filed for e10s (frame rate is about halved when e10s is enabled)?
Updated•11 years ago
|
Flags: needinfo?(garyshap)
Updated•11 years ago
|
Flags: needinfo?(garyshap)
Comment 8•11 years ago
|
||
It's still not fixed and e10s isn't enabled by default yet even on Nightly.
Comment 9•11 years ago
|
||
This should have been fixed by bug 1000640.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•