New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 738588 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 529146
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in blink::ReportFatalErrorInMainThread

Project Member Reported by ClusterFuzz, Jun 30 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5348423799930880

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=5348423799930880


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Cc: msrchandra@chromium.org
Components: Blink>Bindings
Labels: M-61 Test-Predator-Correct-CLs
Owner: gyuyoung...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: gyuyoung
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/46740f4e99de22f90302e72ca3a91730521b5827
Time: Mon Jun 05 05:29:54 2017
Lines 79 of file V8Initializer.cpp which potentially caused crash are changed in this cl (frame #1, "blink::ReportFatalErrorInMainThread").
Minimum distance from crash line to modified line: 0. (file: V8Initializer.cpp, crashed on: 79, modified: 79).

@gyuyoung -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.
Mergedinto: 529146
Status: Duplicate (was: Assigned)
As an  issue 730001 , I think 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 as I did it on the  issue 730001 .

Sign in to add a comment