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

Issue 630564 link

Starred by 1 user
Status: Fixed
Owner:
msramek@chromium.org
Closed: Jul 2016
Cc:
█ roc...@chromium.org
msramek@chromium.org
mpear...@chromium.org
mark@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Massive failure of Mac ASan 64 Tests

Project Member Reported by msramek@chromium.org, Jul 22 2016 
Mac ASan 64 Tests started failing with build #19214:

https://build.chromium.org/p/chromium.memory/builders/Mac%20ASan%2064%20Tests%20%281%29/builds/19214

A large number of tests is affected.

There seem to be two patterns of failure:

================================

[42381:3335:0721/215850:WARNING:vt_video_decode_accelerator_mac.cc(162)] Failed to create VTDecompressionSession: Error Domain=NSOSStatusErrorDomain Code=-8973 "The operation couldn’t be completed. (OSStatus error -8973.)" (codecOpenErr) (-8973)
[42381:3335:0721/215850:WARNING:vt_video_decode_accelerator_mac.cc(197)] Failed to create hardware VideoToolbox session
[42381:3335:0721/215850:ERROR:vt_video_encode_accelerator_mac.cc(539)]  VTCompressionSessionCreate failed: -12908
[42389:14339:0721/215854:FATAL:resource_provider.cc(1360)] Check failed: !delegated_sync_points_required_ || resource->dirty_image || !resource->needs_sync_token().

================================

[42619:3335:0721/215959:WARNING:vt_video_decode_accelerator_mac.cc(162)] Failed to create VTDecompressionSession: Error Domain=NSOSStatusErrorDomain Code=-8973 "The operation couldn’t be completed. (OSStatus error -8973.)" (codecOpenErr) (-8973)
[42619:3335:0721/215959:WARNING:vt_video_decode_accelerator_mac.cc(197)] Failed to create hardware VideoToolbox session
[42619:3335:0721/215959:ERROR:vt_video_encode_accelerator_mac.cc(539)]  VTCompressionSessionCreate failed: -12908
[42616:83971:0721/220000:WARNING:simple_synchronous_entry.cc(1054)] Could not open platform files for entry.
[42616:4099:0721/220001:ERROR:mach_port_broker.mm(180)] Unknown process 42621 is sending Mach IPC messages!
[42616:30467:0721/220001:FATAL:node_channel.cc(774)] Check failed: pending_writes.empty() && pending_relays.empty().

================================

Comment 1 by msramek@chromium.org, Jul 22 2016 

Both failures start in vt_video_decode_accelerator_mac.cc. There is exactly one CL in that build range touching video encode / decode, which is https://codereview.chromium.org/2167333002. This is a reland of previously reverted CL, so there's a good chance it's offending. However, it's been reverted shortly after (https://codereview.chromium.org/2170133003/) and it didn't fix the errors.

Comment 2 by msramek@chromium.org, Jul 22 2016 

Last change to vt_video_encode_accelerator_mac.cc was 13 days ago. It's probable that the error is elsewhere, and that this back-and-forth in the video code only exposed it.

The second failure pattern ends in node_channel.cc, which is in Mojo code. There were several Mojo CLs in the build batch. Will investigate.

Comment 3 by msramek@chromium.org, Jul 22 2016

Cc: roc...@chromium.org
Suspecting https://codereview.chromium.org/2163633003. Will try to revert.

+cc author

Comment 4 by msramek@chromium.org, Jul 22 2016 

The CL had also been reverted once before, which increases my suspicion.

Comment 5 by msramek@chromium.org, Jul 22 2016

Status: Fixed (was: Started)
The bot is green - the suspicion was correct.

Comment 6 by benhenry@chromium.org, Aug 4 2016

Labels: hotlist-infra-opportunity
►

Sign in to add a comment