Issue metadata
Sign in to add a comment
|
Heap-use-after-free in gpu::gles2::GLES2Implementation::OnGpuControlLostContext |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4677658684948480 Fuzzer: ochang_media2 Job Type: mac_asan_chrome Platform Id: mac Crash Type: Heap-use-after-free READ 8 Crash Address: 0x6150000671a8 Crash State: gpu::gles2::GLES2Implementation::OnGpuControlLostContext gpu::CommandBufferProxyImpl::OnChannelError base::debug::TaskAnnotator::RunTask Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=559515:559525 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4677658684948480 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
May 19 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
May 19 2018
,
May 19 2018
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 19 2018
,
May 21 2018
danakj@, could you please and a look and / or help to find an owner?
,
May 30 2018
,
Jun 2 2018
ClusterFuzz has detected this issue as fixed in range 563664:563689. Detailed report: https://clusterfuzz.com/testcase?key=4677658684948480 Fuzzer: ochang_media2 Job Type: mac_asan_chrome Platform Id: mac Crash Type: Heap-use-after-free READ 8 Crash Address: 0x6150000671a8 Crash State: gpu::gles2::GLES2Implementation::OnGpuControlLostContext gpu::CommandBufferProxyImpl::OnChannelError base::debug::TaskAnnotator::RunTask Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=559515:559525 Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=563664:563689 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4677658684948480 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jun 2 2018
ClusterFuzz testcase 4677658684948480 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jun 2 2018
,
Jun 8 2018
,
Jun 8 2018
This bug requires manual review: M68 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: cmasso@(Android), kariahda@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 8 2018
Seems like nothing to merge.
,
Jul 12
,
Sep 8
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, May 19 2018