DCHECK failed when debug build of Chrome is deployed to VM |
|||||
Issue descriptionChrome Version: 70.0.3508.0 OS: ChromeOS on betty What steps will reproduce the problem? (1) Build ChromeOS for betty and start cros_vm https://chromium.googlesource.com/chromiumos/docs/+/master/cros_vm.md#launch-a-locally-built-vm-from-within-the-chroot (2) Build Chrome as debug build and deploy_chrome https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md#Debug-builds What is the expected result? ChromeOS should work well What happens instead? DCHECK fails at the start-up page again and again. User cannot login to ChromeOS. I found an error message and stack trace in /var/log/ui/ui.LATEST like this: [FATAL:video_decode_stats_recorder.cc(39)] Check failed: features->profile != VIDEO_CODEC_PROFILE_UNKNOWN (-1 vs. -1) This comes from https://cs.chromium.org/chromium/src/media/mojo/services/video_decode_stats_recorder.cc?l=39&rcl=e506d0be666b07ac1004f72cd0a84f808a096b8e
,
Aug 3
,
Sep 28
Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.
,
Nov 8
<UI triage> Bug owners, please add the appropriate component to your bug. Thanks!
,
Nov 8
What startup page are we talking about? Does it have a chrome:// url? Hitting the check means we are somehow attempting to record stats for a video codec we don't recognize. Definitely a bug somewhere.
,
Nov 8
,
Nov 9
I meant ChromeOS's login screen, but I cannot reproduce this problem today. So, let me mark "WontFix". Thank you for reminding me. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by keiichiw@chromium.org
, Aug 3