Obsolete
Status Update
Comments
re...@gmail.com <re...@gmail.com> #2
I forgot to mention details of my video driver and desktop:
NVidia driver 304.64, Linux kernel 3.6.6, KDE 4.9.3, X.Org server 1.13.0.
NVidia driver 304.64, Linux kernel 3.6.6, KDE 4.9.3, X.Org server 1.13.0.
do...@gmail.com <do...@gmail.com> #3
I've got the same problem
Flash version: 11.5.31.2
Linux kernel: 3.5.7
KDE: 4.8.5
NVidia drivers: 295.75
X.Org server: 1.12.2
Flash version: 11.5.31.2
Linux kernel: 3.5.7
KDE: 4.8.5
NVidia drivers: 295.75
X.Org server: 1.12.2
[Deleted User] <[Deleted User]> #4
Hello, can you still reproduce it, can you send me a screenshot if possible?
re...@gmail.com <re...@gmail.com> #5
Lack of vertical synchronization creates tearing during animation. A screenshot can't show it. However, Wikipedia has a very well simulated "screenshot" of the effect:
http://en.wikipedia.org/wiki/Screen_tearing
The artifact shown in the picture is exactly what fullscreen Flash video looks like after Chrome v22. Note that in reality the tear point moves randomly up and down, making it even more apparent.
Also note that this only happens when KDE is configured to suspend desktop effects for fullscreen applications, or when disabling desktop effects completely, because when enabled, the video goes through the compositor which is always VSynced and thus no tearing occurs. The best way to reproduce this is by disabling compositing completely. This is done in System Settings, by unchecking the "Enable Desktop Effects at Startup" checkbox in the "Desktop Effects" dialog.
The artifact shown in the picture is exactly what fullscreen Flash video looks like after Chrome v22. Note that in reality the tear point moves randomly up and down, making it even more apparent.
Also note that this only happens when KDE is configured to suspend desktop effects for fullscreen applications, or when disabling desktop effects completely, because when enabled, the video goes through the compositor which is always VSynced and thus no tearing occurs. The best way to reproduce this is by disabling compositing completely. This is done in System Settings, by unchecking the "Enable Desktop Effects at Startup" checkbox in the "Desktop Effects" dialog.
[Deleted User] <[Deleted User]> #6
[Empty comment from Monorail migration]
al...@gmail.com <al...@gmail.com> #7
I have tearing in all of my GNOME 3 experience. It's a NVIDIA driver bug. Try playing video in Totem and you'll probably see that it tears also. Unredirected windows doesn't tear with NVIDIA driver though.
re...@gmail.com <re...@gmail.com> #8
Totem does VSync. Flash does not. That's the problem. GNOME and Totem have nothing to do with any of it.
me...@gmail.com <me...@gmail.com> #9
I have the same problems with 23.0.1271.64 (165188) - tearing in flash, Nvidia drivers (310.19), flash 11.15.31.2.
It's doesn't happen all of the time, I don't run a compositing WM (dwm) so that's not interfering. It's very noticeable as it's the first occurrence of tearing I've had as of yet with pepper flash, took me back to the bad old days of standalone flashplayer!
It's doesn't happen all of the time, I don't run a compositing WM (dwm) so that's not interfering. It's very noticeable as it's the first occurrence of tearing I've had as of yet with pepper flash, took me back to the bad old days of standalone flashplayer!
[Deleted User] <[Deleted User]> #10
[Empty comment from Monorail migration]
je...@gmail.com <je...@gmail.com> #11
This problem has been plaguing me.
Around March of last year it was fixed. Then sometime around October the video
tearing started occurring again after an Nvidia driver update. I don't have
driver version numbers, sorry.
I definitely believe it is an Nvidia driver issue. There is no screen tearing
on my late 2012 Dell XPS 13 Intel hardware with the same software setup and
open source Intel drivers.
Test video:http://www.youtube.com/watch?v=ceX18O9pvLs
Nvidia bug report:https://devtalk.nvidia.com/default/topic/527020/linux/chromium-pepper-flash-full-screen-video-tearing-nvidia-gtx-580/
Chromium bug report:http://code.google.com/p/chromium/issues/detail?id=160454
My current setup:
distro: Arch linux 64bit
chromium: 23.0.1271.97
chromium-pepper-flash: 11.5.31.135
xorg-server: 1.13.1
linux: 3.7.1
openbox: 3.5.0
nvidia 580 GTX: 310.19
Dual ASUS 24" monitors: Ancor Communications Inc. VS248
Nvidia bug report info:http://nvidia.custhelp.com/app/answers/detail/a_id/44
Nvidia Linux support forum:https://devtalk.nvidia.com/default/board/98/linux/
Things I have tried:
I have attempted to enable hardware acceleration in /etc/adobe/mms.cfg, but it
seems to do nothing.
cat /etc/adobe/mms.cfg
# OverrideGPUValidation=1
EnableLinuxHWVideoDecode=1
Right clicking the test video linked above and selecting "Show video info"
shows "software video rendering, software video decoding"
Right clicking the video and choosing "Settings" and checking "Enable hardware
acceleration" has no effect.
"Sync to VBlank" is enabled in nivdia-settings, no effect.
Log output:http://demizerone.com/files/nvidia-bug-report.log.gz
Around March of last year it was fixed. Then sometime around October the video
tearing started occurring again after an Nvidia driver update. I don't have
driver version numbers, sorry.
I definitely believe it is an Nvidia driver issue. There is no screen tearing
on my late 2012 Dell XPS 13 Intel hardware with the same software setup and
open source Intel drivers.
Test video:
Nvidia bug report:
Chromium bug report:
My current setup:
distro: Arch linux 64bit
chromium: 23.0.1271.97
chromium-pepper-flash: 11.5.31.135
xorg-server: 1.13.1
linux: 3.7.1
openbox: 3.5.0
nvidia 580 GTX: 310.19
Dual ASUS 24" monitors: Ancor Communications Inc. VS248
Nvidia bug report info:
Nvidia Linux support forum:
Things I have tried:
I have attempted to enable hardware acceleration in /etc/adobe/mms.cfg, but it
seems to do nothing.
cat /etc/adobe/mms.cfg
# OverrideGPUValidation=1
EnableLinuxHWVideoDecode=1
Right clicking the test video linked above and selecting "Show video info"
shows "software video rendering, software video decoding"
Right clicking the video and choosing "Settings" and checking "Enable hardware
acceleration" has no effect.
"Sync to VBlank" is enabled in nivdia-settings, no effect.
Log output:
me...@gmail.com <me...@gmail.com> #12
Update
It appears that if I navigate to chrome://flags/ and enable the "Override software rendering list" option I no longer get tearing. Somehow after Chromium version 22 some Nvidia setups aren't recognised as valid system configurations for hw decoding.
It appears that if I navigate to chrome://flags/ and enable the "Override software rendering list" option I no longer get tearing. Somehow after Chromium version 22 some Nvidia setups aren't recognised as valid system configurations for hw decoding.
bo...@gmail.com <bo...@gmail.com> #13
Genius!!!! Thanks.
re...@gmail.com <re...@gmail.com> #14
That worked here too. Thank you. At last, videos look OK again.
wo...@gmail.com <wo...@gmail.com> #15
#11: You *rock*. Works a treat here, too.
je...@gmail.com <je...@gmail.com> #16
Works here two, on dual monitors even. Thanks!
bu...@chromium.org <bu...@chromium.org> #17
[Empty comment from Monorail migration]
bu...@chromium.org <bu...@chromium.org> #18
[Empty comment from Monorail migration]
bu...@chromium.org <bu...@chromium.org> #19
[Empty comment from Monorail migration]
jl...@google.com <jl...@google.com> #20
[Comment Deleted]
jl...@chromium.org <jl...@chromium.org> #21
This is also a problem playing HTML5 videos fullscreen on Pixel. I don't believe that it is specific to flash. As mentioned, enabling the "Override software rendering list" flag fixes the problem. What is the argument against enabling this flag by default?
[Deleted User] <[Deleted User]> #22
Hi Pangu,
This is apparently causing problems in Lava as well. Does it make sense to enable the "Override software rendering list" flag by default?
Thanks!
This is apparently causing problems in Lava as well. Does it make sense to enable the "Override software rendering list" flag by default?
Thanks!
re...@chromium.org <re...@chromium.org> #23
@scherkus to provide his thoughts on enabling the flag by default.
[Deleted User] <[Deleted User]> #24
@scherkus Ping for thoughts.
sc...@chromium.org <sc...@chromium.org> #25
punting to wiltzius@ as this sounds certain compositing modes inflict tearing
[Deleted User] <[Deleted User]> #26
If "override software rendering list" solves it, that means these machines are in the legacy software path and that isn't vsync'd, so tearing is expected
jl...@chromium.org <jl...@chromium.org> #27
Should that really be the case for a Pixel? This is a pretty new device, which should have a premium media experience.
wo...@gmail.com <wo...@gmail.com> #28
Or an nvidia 760?
I think the list needs updating.
I think the list needs updating.
ma...@gmail.com <ma...@gmail.com> #29
I have this problem with ubuntu 14.04 and amd a85600k, opensource radeon drivers :/, if I use override software rendering list, my system go slow...and finally freeze :(
rj...@gmail.com <rj...@gmail.com> #30
I also have the issue with Ubuntu 14.04 and the Radeon driver, on a laptop with an RV710 graphics board which may not be the newest around but with 512Mb dedicated memory should be able to play fullscreen streaming Flash video without hiccups ...
Overriding the software rendering list helps a bit but not completely (or should I say, not all the time?).
I'll try to check with some of the test videos on here, as I am under the impression that the shearing occurs also under LMDE on which I kept the legacy proprietary drivers installed.
Overriding the software rendering list helps a bit but not completely (or should I say, not all the time?).
I'll try to check with some of the test videos on here, as I am under the impression that the shearing occurs also under LMDE on which I kept the legacy proprietary drivers installed.
rj...@gmail.com <rj...@gmail.com> #31
Suspicion confirmed. I get shearing also with the proprietary driver, even if it's configured to vsync always. Also in Chrome's HTML5 mode (test video above).
But on this platform there's no shearing in Firefox, which uses the "legacy" Adobe Flash plugin.
It begins to look like the issue is the pepper Flash player after all...
But on this platform there's no shearing in Firefox, which uses the "legacy" Adobe Flash plugin.
It begins to look like the issue is the pepper Flash player after all...
sc...@chromium.org <sc...@chromium.org> #32
[Empty comment from Monorail migration]
ih...@chromium.org <ih...@chromium.org> #33
Obsolete as youtube uses html5 by default.
29...@gmail.com <29...@gmail.com> #34
Not obsolete! HTML5 video also tears in Chrome 42.0.2311.135! Or give a link to bug with htlm5 tearing here.
Enabling "Override software rendering list" does not helps. Also, don't just youtube uses Flash player! Where is many sites, in corporations too, they would use flash many years.
I use Nvidia 820m + Intel (f*cked optimus), and Intel by default. In nvidia-settings I don't have Vsync option. In which configs I must set vsync? No composite manager used, Lubuntu 14.04.2, LXDE.
Enabling "Override software rendering list" does not helps. Also, don't just youtube uses Flash player! Where is many sites, in corporations too, they would use flash many years.
I use Nvidia 820m + Intel (f*cked optimus), and Intel by default. In nvidia-settings I don't have Vsync option. In which configs I must set vsync? No composite manager used, Lubuntu 14.04.2, LXDE.
is...@google.com <is...@google.com> #35
This issue was migrated from crbug.com/chromium/160454?no_tracker_redirect=1
[Multiple monorail components: Blink, Internals>Plugins>Flash]
[Monorail components added to Component Tags custom field.]
[Multiple monorail components: Blink, Internals>Plugins>Flash]
[Monorail components added to Component Tags custom field.]
Description
Steps to reproduce the problem:
1. Go to a video, like
2. Click the fullscreen icon
What is the expected behavior?
Tear-free, VSync'ed video.
What went wrong?
Video lacks VSync and is therefore "tearing."
Example URL:
Does it occur on multiple sites: Yes
Is it a problem playing media? Yes
Is it a problem with a plugin? Yes Pepper Flash
Did this work before? Yes In versions 22.x of Chrome.
Does this work in other browsers? N/A
Chrome version: 24.0.1312.5 Channel: beta
OS Version: