Issue metadata
Sign in to add a comment
|
Abrt in blink::ReportFatalErrorInMainThread |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4983978921820160 Fuzzer: inferno_canvas_wrecker Job Type: linux_asan_chrome_v8_arm Platform Id: linux Crash Type: Abrt Crash Address: 0x00000001 Crash State: blink::ReportFatalErrorInMainThread v8::Uint8ClampedArray::New blink::DOMTypedArray<WTF::Uint8ClampedArray, v8::Uint8ClampedArray>::Wrap Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=476918:476985 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4983978921820160 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 6 2017
Let me fix it soon. It seems that this is a regression by my cleanup patch.
,
Jun 8 2017
I upload a fix - https://codereview.chromium.org/2926093002/
,
Jun 8 2017
According to tkent,this crash was intended. So ClusterFuzz reported as new crash just because the crash message is changed slightly. So I would like to merge this issue into Issue 529146. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by msrchandra@chromium.org
, Jun 6 2017Components: Blink>Bindings
Labels: M-60 Test-Predator-Correct-CLs
Owner: gyuyoung...@chromium.org
Status: Assigned (was: Untriaged)