New issue
Advanced search Search tips

Issue 823038 link

Starred by 3 users
Status: Duplicate
Merged: issue 821240
Owner: ----
Closed: Mar 2018
Cc:
jbroman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in blink::MessagePort::Entangle

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  blink::MessagePort::Entangle
  blink::MessagePort::close
  mojo::Connector::HandleError
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=528060:528062

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 17 2018

Components: Blink>Messaging Internals>Mojo
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, Mar 19 2018

Mergedinto: 821240
Status: Duplicate (was: Untriaged)
This issue looks similar to  bug 821240 , hence merging in to it. Feel free to undupe if it's a different issue.

Thanks!
►

Sign in to add a comment