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

Issue 616680 link

Starred by 2 users
Status: Verified
Owner:
posciak@chromium.org
Closed: Jul 2016
Cc:
emir...@chromium.org
█ wuchengli@chromium.org
mflodman@chromium.org
sprang@chromium.org
brandtr@chromium.org
posciak@chromium.org
terelius@chromium.org
holmer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocked on:
issue chrome-os-partner:53980
Blocking:
issue 615272



Sign in to add a comment

Dtor of V4L2VEA causes a crash on Blaze

Project Member Reported by emir...@chromium.org, Jun 2 2016 
- Join an apprtc loopback call from device Blaze using https://appr.tc/?debug=loopback&vsc=h264
- Wait till the loopback starts

AppRTC loopback starts with 176x144 and frame resolution grows from there based on bandwidth. When VEA is reset due to resizing, we see a crash in gpu process. I added more logging and found out that the crash comes when destructing TegraV4L2Device. See l.1006 in https://paste.googleplex.com/4560652328763392. posciak@, can you delegate it to who would be appropriate?

Comment 1 by wuchengli@chromium.org, Jun 2 2016 

[1282:1282:0601/191315:VERBOSE4:v4l2_video_encode_accelerator.cc(104)] ~V4L2VideoEncodeAccelerator
[1282:1282:0601/191315:VERBOSE3:v4l2_video_encode_accelerator.cc(1237)] DestroyInputBuffers()
[1282:1282:0601/191315:VERBOSE3:v4l2_video_encode_accelerator.cc(1253)] DestroyOutputBuffers()
[1282:1282:0601/191315:VERBOSE4:v4l2_video_encode_accelerator.cc(112)] ~V4L2VideoEncodeAccelerator
[1282:1282:0601/191315:VERBOSE3:tegra_v4l2_device.cc(99)] ~TegraV4L2Device
Received signal 11 SEGV_MAPERR 0000cdcdcdc9
#0 0x0000aecea636 base::debug::StackTrace::StackTrace()
#1 0x0000aecea2dc base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x0000a0f551a0 <unknown>
#3 0x0000aeefab36 DebugDeallocate()
[end of stack trace]
[1:13:0601/191316:ERROR:gpu_video_encode_accelerator_host.cc(253)] Error from Send(../../media/gpu/ipc/client/gpu_video_encode_accelerator_host.cc:266) Send(852104) failed (error = 2)
[1:13:0601/191316:ERROR:gpu_video_encode_accelerator_host.cc(109)] Send(GpuCommandBufferMsg_CreateVideoEncoder()) failed
[1:13:0601/191316:ERROR:rtc_video_encoder.cc(528)] CreateAndInitializeVEA@../../content/renderer/media/rtc_video_encoder.cc:301kInvalidArgumentError - Error initializing video_encoder
[1:13:0601/191316:ERROR:gpu_video_decode_accelerator_host.cc(73)] OnChannelError()
[1:13:0601/191316:VERBOSE2:gpu_video_decode_accelerator_host.cc(184)] PostNotifyError(): error=4
[1:13:0601/191316:ERROR:gpu_video_decode_accelerator_host.cc(73)] OnChannelError()
[1:13:0601/191316:VERBOSE2:gpu_video_decode_accelerator_host.cc(184)] PostNotifyError(): error=4
[1:13:0601/191316:ERROR:rtc_video_decoder.cc(515)] VDA Error:4
[1:13:0601/191316:VERBOSE2:rtc_video_decoder.cc(755)] DestroyVDA

Comment 2 by wuchengli@chromium.org, Jun 2 2016 

Could this be http://crosbug.com/p/50290?

Comment 3 by posciak@chromium.org, Jun 2 2016

Blockedon: chrome-os-partner:53980

Comment 4 by posciak@chromium.org, Jun 2 2016

Components: OS>Kernel>Video
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 2 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by tnakamura@chromium.org, Jun 3 2016

Status: Assigned (was: Untriaged)
posciak@ - I'm setting you as the owner even though this is blocked on that chrome-os-partner bug. Can you reply back here once that issue has been addressed so we know when to retest?

Comment 7 by posciak@chromium.org, Jun 5 2016

Labels: VideoShortList

Comment 9 by ka...@chromium.org, Nov 18 2016

Status: Verified (was: Fixed)
►

Sign in to add a comment