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

Issue 834740 link

Starred by 1 user
Status: WontFix
Owner:
szager@chromium.org
Closed: Sep 5
Cc:
█ brajkumar@chromium.org
lfg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Abrt in blink::ReportFatalErrorInMainThread

Project Member Reported by ClusterFuzz, Apr 19 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5051710981275648

Fuzzer: inferno_twister
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539000041a6
Crash State:
  blink::ReportFatalErrorInMainThread
  ReportApiFailure
  ApiCheck
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=523898:523900

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5051710981275648

Additional requirements: Requires HTTP

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
Project Member

Comment 1 by ClusterFuzz, Apr 19 2018

Components: Blink>Bindings
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Comment 2 by brajkumar@chromium.org, Apr 24 2018

Cc: brajkumar@chromium.org
Labels: -Pri-1 M-66 Test-Predator-Wrong Pri-2
Owner: szager@chromium.org
Status: Assigned (was: Untriaged)
This issue looks similar to  bug 821060 , hence assigning to szager@ for more updates.

Thanks!
Project Member

Comment 3 by ClusterFuzz, Jul 15

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5051710981275648 appears to be flaky, updating reproducibility label.
Project Member

Comment 4 by ClusterFuzz, Sep 5

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5051710981275648 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
►

Sign in to add a comment