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

Issue 771920 link

Starred by 2 users
Status: Assigned
Owner:
posciak@chromium.org
Cc:
█ kqyang@chromium.org
xhw...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Black screens occurs when using wrong encryption key

Project Member Reported by fbeaufort@chromium.org, Oct 5 2017 
Chrome Version       : 63.0.3230.0
OS Version: 10001.0.0

What steps will reproduce the problem?
1. Go to https://beaufortfrancois.github.io/sandbox/media/clearkey
2. Select "VP9 - No clear lead"
3. Check "Wrong Encryption Key"
4. Click "Load & Play" button

What is the expected result?
The encrypted video should not play.

What happens instead of that?
Encrypted video does not play AND my entire screen goes black for 3 seconds ;(

Note that it happens with MSE as well.

See my logs:
[1365:1365:1005/120529.897553:VERBOSE1:drm_display_host_manager.cc(247)] Got display event ADD for /dev/dri/card0
[1365:1365:1005/120529.899211:VERBOSE1:drm_display_host_manager.cc(247)] Got display event ADD for /dev/dri/card1
[1365:28844:1005/120529.899359:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card1 in 0 ms with 1 attempt(s)
[1365:1365:1005/120529.901168:ERROR:gpu_process_transport_factory.cc(975)] Lost UI shared context.
[1365:1365:1005/120530.903774:VERBOSE1:display_configurator.cc(917)] Display snapshots invalidated.
[1365:1365:1005/120530.903834:VERBOSE1:update_display_configuration_task.cc(69)] OnDisplaysUpdated: new_display_state=SINGLE new_power_state=ALL_ON flags=0 force_configure=1 display_count=1
[1365:1365:1005/120530.903869:VERBOSE1:display_configurator.cc(212)] EnterState: display=SINGLE power=ALL_ON
[1365:1365:1005/120531.355089:VERBOSE1:display_configurator.cc(1022)] OnConfigured: success=1 new_display_state=SINGLE new_power_state=ALL_ON

Comment 1 by fbeaufort@chromium.org, Oct 5 2017

Cc: xhw...@chromium.org kqyang@chromium.org

Comment 2 by fbeaufort@chromium.org, Oct 5 2017 

And here are below my system logs when logging is enabled.
(Please ignore timestamps)

2017-10-05T12:40:19.444673+02:00 INFO kernel: [14539.195760] VaapiDecoderThr[4683]: segfault at 76a6db2232fd ip 000076a68934a5fa sp 000076a67f56d070 error 4 in hybrid_drv_video.so[76a689310000+255000]
2017-10-05T12:40:19.465011+02:00 INFO crash_reporter[4699]: Falling back to parsing crash attributes '%P:11:1000:VaapiDecoderThr' without UID
2017-10-05T12:40:19.465050+02:00 ERR crash_reporter[4699]: Invalid parameter: --user=%P:11:1000:VaapiDecoderThr
2017-10-05T12:40:19.468520+02:00 WARNING crash_reporter[4698]: Received crash notification for chrome[4645] user 1000 (called directly)
2017-10-05T12:40:19.869966+02:00 INFO kernel: [14539.617409] atmel_mxt_ts i2c-ATML0001:01: Status: 10 Config Checksum: 7c2fb6
2017-10-05T12:40:19.869980+02:00 INFO kernel: [14539.617421] atmel_mxt_ts i2c-ATML0001:01: Status: 00 Config Checksum: 7c2fb6
2017-10-05T12:40:19.983686+02:00 INFO kernel: [14539.734870] atmel_mxt_ts i2c-ATML0001:01: Status: 10 Config Checksum: 7c2fb6
2017-10-05T12:40:19.987673+02:00 INFO kernel: [14539.739465] atmel_mxt_ts i2c-ATML0001:01: Status: 00 Config Checksum: 7c2fb6
2017-10-05T12:40:20.933693+02:00 INFO kernel: [14540.686303] atmel_mxt_ts i2c-ATML0001:01: Status: 10 Config Checksum: 7c2fb6
2017-10-05T12:40:20.944694+02:00 INFO kernel: [14540.697241] atmel_mxt_ts i2c-ATML0001:01: Status: 00 Config Checksum: 7c2fb6

Comment 3 by xhw...@chromium.org, Oct 5 2017 

Assuming you are on ChromeOS, which device are you using?

Comment 4 by fbeaufort@chromium.org, Oct 6 2017 

I've gathered these logs on a Chromebook Pixel 2015.

Note that I can reproduce as well on a HP Chromebook 14 (2013) - Stable channel.

Comment 5 by xhw...@chromium.org, Oct 13 2017

Cc: posciak@chromium.org
posciak: Please note the "my entire screen goes black for 3 seconds" part, which seems like a ChromeOS bug. Basically we are using a wrong decryption key so we are kinda feeding garbage to the video decoder.

Comment 6 by yini...@chromium.org, Oct 31 2017

Cc: -posciak@chromium.org
Owner: posciak@chromium.org
Status: Assigned (was: Unconfirmed)
I couldn't repro it on ChromeOS LINK device 63.0.3236.0. it seems only repro on specific CrOS device.

Comment 7 Deleted

Comment 8 by fbeaufort@chromium.org, Nov 9 2017 

I can still reproduce with:

Google Chrome	64.0.3261.0 (Official Build) canary (64-bit)
Platform	10106.0.0 (Official Build) canary-channel samus

(I don't have access to the HP Chromebook 14 for now.)

But NOT with:

Google Chrome	64.0.3261.0 (Official Build) canary (64-bit)
Platform	10109.0.0 (Official Build) canary-channel eve

Google Chrome	61.0.3163.123 (Official Build) (32-bit)
Platform	9765.85.0 (Official Build) stable-channel kevin

Google Chrome	61.0.3163.120 (Official Build) (32-bit)
Platform	9765.81.0 (Official Build) stable-channel link

Comment 9 by fbeaufort@chromium.org, Nov 10 2017 

And I can reproduce with:

Google Chrome	61.0.3163.123 (Official Build) (64-bit)
Platform	9765.85.0 (Official Build) stable-channel falco

See about:gpu full page at https://drive.google.com/a/google.com/file/d/1lTfLTiErf-_msRod3RfHeDamNjqSRiQX/view?usp=sharing

Logs:

Log Messages
[32264:32270:1110/084403.468864:VERBOSE1:drm_device_manager.cc(54)] : Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1
[32264:32270:1110/084404.518481:VERBOSE1:drm_display.cc(102)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=28 origin=0,0 size=1366x768
GpuProcessHostUIShim: The GPU process crashed!
[357:357:1110/084459.336502:ERROR:gles2_cmd_decoder.cc(17788)] : [.DisplayCompositor-0xbddd81af600]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[357:357:1110/084459.336608:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084459.336685:ERROR:gles2_cmd_decoder.cc(17788)] : [.DisplayCompositor-0xbddd81af600]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[357:357:1110/084459.336723:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084459.336781:ERROR:gles2_cmd_decoder.cc(17788)] : [.DisplayCompositor-0xbddd81af600]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[357:357:1110/084459.336811:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:364:1110/084500.208738:VERBOSE1:drm_display.cc(102)] : DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=28 origin=0,0 size=1366x768
[357:357:1110/084502.515084:ERROR:gles2_cmd_decoder.cc(17788)] : [.DisplayCompositor-0xbddd81af600]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[357:357:1110/084502.515322:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084502.515521:ERROR:gles2_cmd_decoder.cc(17788)] : [.DisplayCompositor-0xbddd81af600]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[357:357:1110/084502.515690:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084502.515864:ERROR:gles2_cmd_decoder.cc(17788)] : [.DisplayCompositor-0xbddd81af600]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[357:357:1110/084502.516022:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084502.516205:ERROR:gles2_cmd_decoder.cc(17788)] : [.DisplayCompositor-0xbddd81af600]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[357:357:1110/084502.516376:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084502.516558:ERROR:gles2_cmd_decoder.cc(17788)] : [.DisplayCompositor-0xbddd81af600]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[357:357:1110/084502.516726:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084502.553935:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084502.554310:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084502.554504:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084502.554657:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[357:357:1110/084502.554806:ERROR:gles2_cmd_decoder.cc(9798)] : [.DisplayCompositor-0xbddd81af600]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
►

Sign in to add a comment