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

Issue 816277 link

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



Sign in to add a comment

Direct-leak in blink::Node::SetLayoutObject

Project Member Reported by ClusterFuzz, Feb 25 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6161845648621568

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

Crash Type: Direct-leak
Crash Address: 
Crash State:
  blink::Node::SetLayoutObject
  blink::Document::Initialize
  blink::LocalDOMWindow::InstallNewDocument
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=209699:209703

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

Additional requirements: Requires Gestures

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, Feb 28 2018

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

Thanks!

Comment 2 by e...@chromium.org, Feb 28 2018

Status: WontFix (was: Untriaged)
Unable to reproduce and no regression range. Unactionable.
Project Member

Comment 3 by ClusterFuzz, Mar 8 2018

Labels: Needs-Feedback
ClusterFuzz testcase 6161845648621568 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