Issue 127374 in chromium: Chrome hardware acceleration

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Feature-GPU Pri-2 Type-Bug Area-Undefined

New issue 127374 by k.khaz...@3rocksgames.com: Chrome hardware acceleration
http://code.google.com/p/chromium/issues/detail?id=127374

OS Version: Windows 7
Exact GPU vendor/model: (attached)
URLs (if applicable): N/A
Other browsers tested: All other browsers
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:

What steps will reproduce the problem?
1.Use canvas
2.Use 2D context
3.Do a graphically expensive process e.g. DrawImage(....);
4.Do the following test once with low graphical power or low end graphics
card and again with high performance graphics card.
5.Create var D1 = new Data();
6.Draw images as explained in 3 above multiple times (loop).
7.After drawing the images get the Date() object again (say D2).
8.Deduct D1 from D2 and get the time it takes in ms to complete the draw
process.

What is the expected result?
We expect to complete the drawing process easily, smoothly and quickly
(despite your graphics card power).

What happens instead?
If you have a low end graphic card Chrome will still attempt to get its
processing power from it and so the drawing time become very very long.
Although, this is an attempt to accelerate the the speed of the graphical
processing we end up making it very slow instead.

Please provide any additional information. Attach a screenshot if
possible.

We propose the following:

1. Chrome must be smart enough to check the speed of the CPU vs GPU and get
the graphical processing power from the one that is most effective.

2. We should be given the ability to insert a command into our code which
if detected by chrome, hardware acceleration is disabled. Many users are
not technically advanced so we cant ask them to perform a manual procedure
to disable hardware acceleration when they use our web services that has
high graphical dependency.

Please copy the contents of about:gpu (chrome://gpu/) below:
----NOTE---> we have manually disabled the hardware acceleration <---
Graphics Feature Status
Canvas: Software only. Hardware acceleration disabled.
HTML Rendering: Hardware accelerated
3D CSS: Hardware accelerated
WebGL: Hardware accelerated
WebGL multisampling: Hardware accelerated
Problems Detected
Accelerated 2D canvas is unavailable: either disabled at the command line
or not supported by the current system.
Version Information
Data exported Wed May 09 2012 10:52:16 GMT+0300 (Arab Standard Time)
Chrome version 18.0.1025.168 (Official Build 134367) m
Operating system Windows NT 6.1 SP1
Software rendering list version 1.25
ANGLE revision 988
2D graphics backend Skia
Performance Information
Graphics 5.9
Gaming 6.9
Overall 5.9
Driver Information
Initialization time 47
Vendor Id 0x8086
Device Id 0x0116
Optimus true
Driver vendor Intel Corporation
Driver version 8.15.10.2696
Driver date 3-19-2012
Pixel shader version 3.0
Vertex shader version 3.0
GL version
GL_VENDOR
GL_RENDERER
GL_VERSION
GL_EXTENSIONS
Diagnostics
0
b3DAccelerationEnabled true
b3DAccelerationExists true
bAGPEnabled true
bAGPExistenceValid true
bAGPExists true
bCanRenderWindow true
bDDAccelerationEnabled true
bDriverBeta false
bDriverDebug false
bDriverSigned false
bDriverSignedValid false
bNoHardware false
dwBpp 32
dwDDIVersion 10
dwHeight 900
dwRefreshRate 40
dwWHQLLevel 0
dwWidth 1600
iAdapter 0
lDriverSize 8087040
lMiniVddSize 0
szAGPStatusEnglish Enabled
szAGPStatusLocalized Enabled
szChipType Intel(R) HD Graphics Family
szD3DStatusEnglish Enabled
szD3DStatusLocalized Enabled
szDACType Internal
szDDIVersionEnglish 10.1
szDDIVersionLocalized 10.1
szDDStatusEnglish Enabled
szDDStatusLocalized Enabled
szDXVAHDEnglish Supported
szDXVAModes ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C
szDescription Intel(R) HD Graphics 3000
szDeviceId 0x0116
szDeviceIdentifier {D7B78E66-4256-11CF-D969-9D24B7C2C535}
szDeviceName \\.\DISPLAY1
szDisplayMemoryEnglish 1696 MB
szDisplayMemoryLocalized 1696 MB
szDisplayModeEnglish 1600 x 900 (32 bit) (40Hz)
szDisplayModeLocalized 1600 x 900 (32 bit) (40Hz)
szDriverAssemblyVersion 8.15.10.2696
szDriverAttributes Final Retail
szDriverDateEnglish 3/19/2012 23:31:56
szDriverDateLocalized 19/03/2012 11:31:56 PM
szDriverLanguageEnglish English
szDriverLanguageLocalized English
szDriverModelEnglish WDDM 1.1
szDriverModelLocalized WDDM 1.1
szDriverName
igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32
szDriverNodeStrongName
oem178.inf:IntelGfx.NTamd64.6.0:iSNBM0:8.15.10.2696:pci\ven_8086&dev_0116
szDriverSignDate
szDriverVersion 8.15.0010.2696
szKeyDeviceID Enum\PCI\VEN_8086&DEV_0116&SUBSYS_04911028&REV_09
szKeyDeviceKey
\Registry\Machine\System\CurrentControlSet\Control\Video\{CD79B09B-6C1F-4A70-88CD-F25F3BB8E0D7}\0000
szManufacturer Intel Corporation
szMiniVdd n/a
szMiniVddDateEnglish n/a
szMiniVddDateLocalized n/a
szMonitorMaxRes
szMonitorName Generic PnP Monitor
szNotesEnglish No problems found.

szNotesLocalized No problems found.

szOverlayEnglish Supported
szRankOfInstalledDriver 00E62001
szRegHelpText
szRevision
szRevisionId 0x0009
szSubSysId 0x04911028
szTestResultD3D7English Not run
szTestResultD3D7Localized Not run
szTestResultD3D8English Not run
szTestResultD3D8Localized Not run
szTestResultD3D9English Not run
szTestResultD3D9Localized Not run
szTestResultDDEnglish Not run
szTestResultDDLocalized Not run
szVdd n/a
szVendorId 0x8086
Log Messages
[1200:9240:4211964:INFO:gpu_child_thread.cc(110)] :
gpu_info_collector::CollectGraphicsInfo complete. success = 1
[8576:11024:7265231:INFO:gpu_child_thread.cc(110)] :
gpu_info_collector::CollectGraphicsInfo complete. success = 1

Attachments:
DxDiag.txt 37.8 KB

[chro...@googlecode.com]

Comment #1 on issue 127374 by vange...@google.com: Chrome hardware
acceleration
http://code.google.com/p/chromium/issues/detail?id=127374

Using Date() to compute draw times is not going to give you accurate
results. The reason being that in the gpu path the expensive part of the
draw (rasterization) doesn't happen synchronously with the calls. That's
why we usually recommend the approach taken by jsgamebench which is to see
how many draw operations you can cram in at a specific framerate.

That being said, we're continuously working on improving performance of the
accelerated canvas implementation. If you have a specific example that
demonstrates that the s/w path is faster than h/w please let us know. The
gpu path should in general be orders of magnitude faster than s/w in
drawImage operations.

We've discussed #2 at length before and the general consensus by multiple
browser vendors is that allowing the app to explicitly opt out of the h/w
accelerated path is not a good idea.

I'm going to close this bug now. If you have an example that demonstrates
how the accelerated path is slower than s/w, please feel free to open a new
one.

[chro...@googlecode.com]

Comment #3 on issue 127374 by toni.m.k...@gmail.com: Chrome hardware
acceleration
http://code.google.com/p/chromium/issues/detail?id=127374

What this means below and is it possible to enable Hardware Acceleration
somehow?

Rasterization: Software only. Hardware acceleration disabled.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings