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

Issue 822618 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
yukishiino@chromium.org
ifratric@google.com
peria@chromium.org
█ brajkumar@chromium.org
lfg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in Create

Project Member Reported by ClusterFuzz, Mar 16 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6501763721723904

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  Create
  blink::ModulesInitializer::InstallSupplements
  blink::LocalDOMWindow::InstallNewDocument
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=209324:209352

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

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, Mar 16 2018

Cc: brajkumar@chromium.org
Components: Blink
Labels: M-65 Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also observing no CL under regression range, hence adding appropriate label and leaving it as untriaged for further updates.

Thanks!

Comment 2 by dtapu...@chromium.org, Mar 20 2018

Components: -Blink Blink>Bindings

Comment 3 by raphael....@intel.com, Mar 21 2018

Cc: peria@chromium.org yukishiino@chromium.org

Comment 4 by jbroman@chromium.org, Mar 21 2018

Status: WontFix (was: Untriaged)
Unable to reproduce, and the reduced test case is massive. It's unlikely that this report will prove actionable.
Project Member

Comment 5 by ClusterFuzz, Mar 28 2018

Labels: Needs-Feedback
ClusterFuzz testcase 6501763721723904 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
►

Sign in to add a comment