Issue 456461 in chromium: Hardware Acceleration not working anymore even when forced - Intel GMA 3150

187 views
Skip to first unread message

chro...@googlecode.com

unread,
Feb 7, 2015, 7:07:01 AM2/7/15
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Cr-Internals-Media Pri-2 Via-Wizard Type-Bug OS-Windows

New issue 456461 by mustafae...@gmail.com: Hardware Acceleration not
working anymore even when forced - Intel GMA 3150
https://code.google.com/p/chromium/issues/detail?id=456461

UserAgent: Mozilla/5.0 (Windows NT 6.3) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/40.0.2214.111 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Open any page with HTML5 or Flash video on it
2.
3.

What is the expected behavior?
Video is displayed smooth and properly.

What went wrong?
Video is played pixlated with jagged lines and skips a lot of frames.

With a clean cache, YouTube videos are displayed correctly like before but
after clicking on re-size or full-screen button, they get pixlated and even
after re-sizing again, going back to small view or refreshing the page it
doesn't fix!

This wasn't the case before Chrome 40. Prior to this version it would fix
by turning on the "Override software rendering list" and "Disable 3D
software rasterizer" flags, but now even turning these on won't fix the
issue.

I've tried Chrome re-installations, Windows re-installation, trying on
Windows 10 and 8.1, Creating new profiles with no extensions, driver
re-installation, plugin disabling-enabling, Forcing Flash or HTML5 player
on YouTube, resetting flags none works!

I don't face this issue on Comodo Chromium 36 or Pale Moon or IE 11, only
on Chrome 40 (also tried Canary 41 and it also has this issue).

Attached Files are in order:
1. Before clicking on re-size or full-screen (with cache cleared)
2. After clicking on re-size button for larger player
3. After going full-screen
4. Comodo Chroumium, after clicking on re-size

Did this work before? Yes Before Chrome 40.

Is it a problem with Flash or HTML5? Both

Does this work in other browsers? Yes

Chrome version: 40.0.2214.111 Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 16.0 r0

GPU Info:
Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Force enabled
Rasterization: Hardware accelerated
Threaded Rasterization: Enabled
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
WebGL: Hardware accelerated

Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_d3d11
exit_on_context_lost
scalarize_vec_and_mat_constructor_args
texsubimage2d_faster_than_teximage2d

Data exported 2/7/2015, 3:27:51 PM
Chrome version Chrome/40.0.2214.111
Operating system Windows NT 6.3
Software rendering list version 0
Driver bug list version 7.12
ANGLE commit id d77bd1632e4c
2D graphics backend Skia
Command Line Args Files\Google\Chrome\Application\chrome.exe"
--flag-switches-begin --disable-software-rasterizer
--enable-centered-app-list --enable-experimental-canvas-features
--enable-experimental-web-platform-features --google-profile-info
--javascript-harmony --enable-material-design-ntp
--disable-offline-auto-reload-visible-only --enable-quic --enable-spdy4
--enable-tab-audio-muting --enhanced-bookmarks-experiment=1
--ignore-gpu-blacklist --max-tiles-for-interest-area=512
--num-raster-threads=4 --enable-origin-chip-on-srp
--enable-search-button-in-omnibox-for-str-or-iip --flag-switches-end

Driver Information
Initialization time 7280
Sandboxed false
GPU0 VENDOR = 0x8086, DEVICE= 0xa011
Optimus false
AMD switchable false
Desktop compositing Aero Glass
Driver vendor Intel Corporation
Driver version 8.15.10.2697
Driver date 3-11-2013
Pixel shader version 2.0
Vertex shader version 0.0
Machine model name
Machine model version
GL_VENDOR Google Inc.
GL_RENDERER ANGLE (Intel(R) Graphics Media Accelerator 3150 (Microsoft
Corporation - WDDM 1.0) Direct3D9Ex vs_0_0 ps_2_0)

------
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 9
dwHeight 600
dwRefreshRate 60
dwWHQLLevel 0
dwWidth 1024
iAdapter 0
lDriverSize 3816840
lMiniVddSize 0
szAGPStatusEnglish Enabled
szAGPStatusLocalized Enabled
szChipType Intel(R) Graphics Media Accelerator 3150
szD3DStatusEnglish Enabled
szD3DStatusLocalized Enabled
szDACType Internal
szDDIVersionEnglish 9Ex
szDDIVersionLocalized 9Ex
szDDStatusEnglish Enabled
szDDStatusLocalized Enabled
szDXVAHDEnglish Not Supported
szDXVAModes ModeMPEG2_A ModeMPEG2_C
szDescription Intel(R) Graphics Media Accelerator 3150 (Microsoft
Corporation - WDDM 1.0)
szDeviceId 0xA011
szDeviceIdentifier {D7B78E66-E351-11CF-1179-1024A1C2C535}
szDeviceName \\.\DISPLAY1
szDisplayMemoryEnglish 256 MB
szDisplayMemoryLocalized 256 MB

------
I guess it used to say Driver Signed on this page before Chrome 40, The
driver is downloaded through Microsoft Update and is the newest, I also
tried the Driver setup from Intel but it didn't fix this issue.

Attachments:
before-fullscreen.jpg 168 KB
after-clicking-resize.jpg 116 KB
after-fullscreen.jpg 123 KB
comodochromium.jpg 103 KB

--
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

chro...@googlecode.com

unread,
Feb 19, 2015, 4:03:15 AM2/19/15
to chromi...@chromium.org

Comment #3 on issue 456461 by mustafae...@gmail.com: Hardware Acceleration
not working anymore even when forced - Intel GMA 3150
https://code.google.com/p/chromium/issues/detail?id=456461

I had installed an extension which forced AVC stream on my previous
comment, here's another one incognito without extensions using VP9 but
still I'm experiencing issues and as you can see a lot of skipped/dropped
frames.

Attachments:
stats-for-nerds-2.png 384 KB

chro...@googlecode.com

unread,
Feb 26, 2015, 4:01:59 AM2/26/15
to chromi...@chromium.org
Updates:
Cc: tkonch...@chromium.org
Labels: Needs-Feedback

Comment #4 on issue 456461 by tkonch...@chromium.org: Hardware Acceleration
not working anymore even when forced - Intel GMA 3150
https://code.google.com/p/chromium/issues/detail?id=456461

Unable to repro the issue on win8 chrome version 43.0.2315.0 and
40.0.2214.111 - could not see any issue when video is fullscreen or after
click

COuld you please upgrade to latest stable 40.0.2214.115 and let us know if
the issue still exists

chro...@googlecode.com

unread,
Feb 26, 2015, 8:14:17 AM2/26/15
to chromi...@chromium.org

Comment #5 on issue 456461 by mustafae...@gmail.com: Hardware Acceleration
not working anymore even when forced - Intel GMA 3150
https://code.google.com/p/chromium/issues/detail?id=456461

@tkonch...@chromium.org, I tested again with cache cleared, extensions
disabled and then uninstalled Chrome v40 and installed Version 39 and
tested again even without changing the HW Acceleration force flags set.
Please pay attention to edges and dropped frames stats.The screenshots are
attached.

I read somewhere on your forums that Chrome requires at least OpenGL 2.1
support to run properly, the latest drivers for Intel GMA 3150 are released
back in 2010 support only up to OpenGL 1.4 but still I had less issues on
Chrome 39 and earlier versions.

Screenshots in order:

1. Fullscreen view on Chrome 40.0.2214.115
2. Fullscreen with stats on v40.0.2214.115
3. Chrome 40 version info
4. Fullscreen view on Chrome 39.0.2171.65
5. Fullscreen view with stats on v39.0.2171.65
6. Chrome 39 version info

Attachments:
scnshot-fullscreen-v40.png 332 KB
scnshot-stats-v40.png 251 KB
scnshot-version-40.png 105 KB
scnshot-fullscreen-v39.png 519 KB
scnshot-stats-v39.png 402 KB
scnshot-version-39.png 101 KB

chro...@googlecode.com

unread,
Feb 26, 2015, 8:41:16 AM2/26/15
to chromi...@chromium.org

Comment #6 on issue 456461 by mustafae...@gmail.com: Hardware Acceleration
not working anymore even when forced - Intel GMA 3150
https://code.google.com/p/chromium/issues/detail?id=456461

If it helps I've attached the GPU Stats Page on Chrome 39.

Attachments:
gpu.html 31.9 KB

chro...@googlecode.com

unread,
Mar 5, 2015, 5:56:22 AM3/5/15
to chromi...@chromium.org

Comment #8 on issue 456461 by mustafae...@gmail.com: Hardware Acceleration
not working anymore even when forced - Intel GMA 3150
https://code.google.com/p/chromium/issues/detail?id=456461

yini...@, I launched the latest stable version of Chrome 41.0.2272.76 with
the command you provided but it didn't fix any of issues,
although "disable_d3d11" was already in Driver Bug Workarounds list on GPU
page.

As a side note, Chrome 41 on a fresh install with default settings will not
use hardware acceleration at all with an error that says "GPU process was
unable to boot: GPU process launch failed."!! I have attached the GPU info
screen as a PDF. Even turning on the flags won't change the Status message
to "Hardware Accelerated".

Attachments:
chrome___gpu.pdf 124 KB

chro...@googlecode.com

unread,
Mar 5, 2015, 6:31:31 AM3/5/15
to chromi...@chromium.org

Comment #9 on issue 456461 by mustafae...@gmail.com: Hardware Acceleration
not working anymore even when forced - Intel GMA 3150
https://code.google.com/p/chromium/issues/detail?id=456461

yini...@, I launched the latest stable version of Chrome 41.0.2272.76 with
the command you provided but it didn't fix any of issues,
although "disable_d3d11" was already in Driver Bug Workarounds list on GPU
page.

chro...@googlecode.com

unread,
Mar 6, 2015, 3:21:59 PM3/6/15
to chromi...@chromium.org
Updates:
Cc: renganat...@chromium.org

Comment #10 on issue 456461 by yini...@chromium.org: Hardware Acceleration
not working anymore even when forced - Intel GMA 3150
https://code.google.com/p/chromium/issues/detail?id=456461

renganathan@, this is VP9 playback having jaggy line and dropped frame
issue that dale said you are working with. can you take a look to see if
there is a primary bug it can dup to?
Reply all
Reply to author
Forward
0 new messages