Deal with java exceptions thrown in media::MediaCodecUtil::IsKnownUnaccelerated |
|||||||
Issue descriptionThere is already a bug open for this call stack: crbug.com/674314 where Torne found some exceptions that might have caused this (by querying for Chrome crashes with similar call stacks). Given that we should see these exceptions in Chrome anyway, should we just leave this one be? AFAICT this thread is not backed by Java either.
,
May 8 2017
Moving to "available" as per new bug triaging guidelines
,
May 9 2017
Thanks Nate!
,
May 9 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 9 2018
this is from our own code, and should crash
,
May 9 2018
I don't think this should crash - we should probably just catch and handle/ignore the exception in Java instead of letting it propagate to native in the first place. This is one of those areas where vendor code may throw undocumented exceptions and we just have to deal with it.
,
May 9 2018
,
May 9 2018
which is tracked in crbug.com/674314?
,
May 9 2018
Yeah. Thanks for spotting that Bo! |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by gsennton@chromium.org
, May 8 2017