New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2013
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment
link

Issue 141737: Tab hangs when playing a Vimeo playlist in the couch mode

Reported by rohi...@chromium.org, Aug 9 2012 Project Member

Issue description

Google Chrome	21.0.1180.78 (Official Build 150695) beta
Platform	2465.116.0 (Official Build) beta-channel stumpy
WebKit	537.1 (@124502)
JavaScript	V8 3.11.10.18
Flash	11.3.31.226

My stumpy is connected to Dell 30" using DP-DP cable. 

What steps will reproduce the problem?
1. Navigate to http://vimeo.com/couchmode/evosia/videos/sort:date/47015825 .
2. Let the playlist play.

What is the expected result?
2.1 The playlist plays fine. Tab doesn't hang.

What happens instead?
2.2 After 20-40 minutes, display sleeps, videos stop playing and eventually unresponsive tab dialog pops up.

Note: These are HTML5 videos. I will attach the logs to this issue.
 

Comment 2 by piman@chromium.org, Aug 10 2012

Cc: posciak@chromium.org
Owner: fischman@chromium.org

Comment 3 by fischman@chromium.org, Aug 10 2012

IDK what to do with the system logs.  Can you repro and get a dump or stacktrace from the hung renderer?

FTR, this is m21, so HW video decode is not enabled by default, so this is unlikely to be a VAVDA/VAAPI issue.

Comment 4 by piman@chromium.org, Aug 10 2012

Cc: zelidrag@chromium.org
BTW, I don't know if it's been fixed yet, but some crash reports showed that video decode *was* enabled on 21. See e.g. http://crash.corp.google.com/reportdetail?reportid=10584f98c3d90419#crashing_thread

Comment 5 by fischman@chromium.org, Aug 10 2012

piman@: I'm pretty sure that required a cmdline switch (--enable-accelerated-video-decode), which sadly doesn't show up in the crash report (for ptype==gpu-process) because the switch wasn't mentioned in GpuProcessHost::LaunchGpuProcess(), because it was only inspected in the renderer.

rohitbm: are you specifying --enable-accelerated-video-decode or have it enabled in about:flags?

Comment 6 by rohi...@chromium.org, Aug 10 2012

I am not explicitly enabling any flags.  I don't find '--enable-accelerated-video-decode' in about: output and in  /sbin/session_manager_setup.sh.

>> Can you repro and get a dump or stacktrace from the hung renderer?
I am testing on a recovery image. Will install a test image and try to get a stack trace.

Comment 7 by rohi...@chromium.org, Aug 10 2012

I started the playlist running on a test image. The hang is not yet reproduced.

Comment 8 by rohi...@chromium.org, Aug 11 2012

I have a process hang reproduced. When I try to attach the hung process to GDB, I get an error 'ptrace: Operation not permitted'.

Comment 9 by rohi...@chromium.org, Aug 11 2012

It works via ssh. I will try to symbolicate the stack trace.

Comment 10 by saintlou@chromium.org, Aug 11 2012

Status: Assigned

Comment 11 by rohi...@chromium.org, Aug 11 2012

We just found that this hang happens only when particular video is above to start. Navigating to below links repros the problem in 15-20 minutes.

http://vimeo.com/couchmode/evosia/videos/sort:date/6098143

I have attached the stack trace. piman@ says that there is nothing obvious in the trace. 
When tab hangs, Chrome window is functional, but tab contents are non-accessible. The mouse pointer doesn't change on hovering over links.
bt.txt
14.1 KB View Download

Comment 12 by fischman@chromium.org, Aug 11 2012

rohitbm: can you verify whether this is using HW decode?
Start a video, and load chrome://histograms/Media.G *twice*.  If no histogram shows up, HW decode is not being used.  If a non-0 bucket is non-empty, then HW decode was attempted and failed to initialize (so pipeline fell back to SW decode).  If the 0-bucket is non-empty, you're using HW decode.

I'm curious what happens if you silence the video by hiding the audio device (chmod).  Does that affect the hangability of your repro?

Comment 13 by fischman@chromium.org, Aug 14 2012

Labels: Action-FeedbackNeeded

Comment 14 Deleted

Comment 15 by rohi...@chromium.org, Aug 14 2012

Nope, there are no histograms for  chrome://histograms/Media.G when playing these videos.

Comment 16 by fischman@chromium.org, Aug 14 2012

@rohitbm: thanks; that means HW decode isn't being used.
I'm failing to repro this on a lumpy running m22 (and don't have a 21 handy).  Have you seen it happen on 22 or 23?

Comment 17 by rohi...@chromium.org, Aug 14 2012

@Ami, I started running this test on R23. Will update this issue with the results.

Comment 18 by rohi...@chromium.org, Aug 14 2012

There are other gpu crashes on R22 and R23 which may not give exact result for this hang.

Comment 19 by fischman@chromium.org, Aug 27 2012

@rohitbm: any update from comment #17 (testing on R23)?

Comment 20 by fischman@chromium.org, Aug 28 2012

Owner: rohi...@chromium.org

Comment 21 by rohi...@chromium.org, Aug 29 2012

Google Chrome	23.0.1247.1 (Official Build 153663) dev
Platform	2816.0.0 (Official Build) dev-channel stumpy
WebKit	537.8 (@126759)
JavaScript	V8 3.13.3.1
Flash	11.3.31.324

I am not able to repro the tab hang problem with R23 ToT build. Do we want to close this issue in this case?

chrome://histograms/Media.G output:
Stats as of last page load;reload to get stats as of this page load.

Histogram: Media.GpuVideoDecoderInitializeStatus recorded 3 samples, average = 0.0 (flags = 0x1)
0  ------------------------------------------------------------------------O (3 = 100.0%)
1  ...

Comment 22 by posciak@chromium.org, Aug 29 2012

This would mean that switching to HW decode fixed the problem, wouldn't it?
Should we try running Chrome with --disable-accelerated-video-decode to see if this still happens on SW in 23?

Comment 23 by bugdroid1@chromium.org, Mar 10 2013

Project Member
Labels: -Area-UI -Feature-GPU -Mstone-21 Cr-Internals-GPU Cr-UI M-21

Comment 24 by rohi...@chromium.org, May 14 2013

Status: WontFix
Closing this. Will open a new issue if we see this again.

Sign in to add a comment