Issue metadata
Sign in to add a comment
|
Crash in cc::Layer::SetNeedsDisplayRect |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4912106726752256 Fuzzer: phoglund_webrtc_peerconnection Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x00000348d2b2 Crash State: cc::Layer::SetNeedsDisplayRect base::internal::Invoker<base::internal::BindState<void base::internal::IncomingTaskQueue::RunTask Sanitizer: thread (TSAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=547728:547729 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4912106726752256 Additional requirements: Requires HTTP Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Apr 4 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
,
Apr 4 2018
,
Apr 4 2018
The crash stack trace turns out to be the same as https://clusterfuzz.com/testcase?key=6543195081801728
,
Jul 13
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 sheriffbot@chromium.org
, Apr 4 2018