New issue
Advanced search Search tips

Issue 608610 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in blink::reportFatalErrorInMainThread

Project Member Reported by ClusterFuzz, May 3 2016

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5745802781130752

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_media
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x00009f7537dd
Crash State:
  blink::reportFatalErrorInMainThread
  v8::Utils::ApiCheck
  v8::internal::V8::FatalProcessOutOfMemory
  

Minimized Testcase (1.42 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94JwRHvPB93FxTVRzSJMRJaXJTWx-1cbdhf6A9FrllmzMMWfSLgunpAnQwH37W-qcAwoSJZV0dfH1rGNElkK3NwBBC9SNnDOO4RJbjAxEg7Q49Y8IldS8uddnbE4hsQgBv_zEYgRUg_QlLC5UTVQfiEZuMc1w

Additional requirements: Requires HTTP

Filer: brajkumar

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Cc: jochen@chromium.org
Labels: findit-wrong Te-Logged
Status: Assigned (was: Available)
Through code search on file "api.cc" from frame #3 suspecting the below change
Review URL: hhttps://codereview.chromium.org/1873443002

Observed some recent changes on this file so assigning to the reviewer, since the author is out of google unable to assign directly.

Jochen@ - Could you please check if this is caused with respect to this change, if not please help us in reassign the issue to the right owner.

Thanks!
Components: Blink>JavaScript
Status: WontFix (was: Assigned)
Array(#large int).join() is expected to run OOM
Project Member

Comment 4 by ClusterFuzz, Jun 4 2016

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5745802781130752

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_media
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x00009f7537dd
Crash State:
  blink::reportFatalErrorInMainThread
  v8::Utils::ApiCheck
  v8::internal::V8::FatalProcessOutOfMemory
  

Minimized Testcase (1.42 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95jaGagEZBwFacq0esaFaJCe_9xN44-luqr3Vn1_sZqAxuLKuN8CVhW5w3AVgaEAvHHW9-YP4ib3uxjawUorIFpQJAnNrs1nz_3s3Z2M6LPB8UlsxB_BkugVtKO-QaoxVdIzS0C16NDYf3VGlGclWdrCnBreA

Additional requirements: Requires HTTP

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment