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

Issue 821363 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 810595
Owner:
please use my google.com address
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Indirect-leak in mojo::internal::InterfacePtrStateBase::InitializeEndpointClient

Project Member Reported by ClusterFuzz, Mar 13 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5725727119638528

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  mojo::internal::InterfacePtrStateBase::InitializeEndpointClient
  mojo::internal::InterfacePtrState<ukm::mojom::UkmRecorderInterface>::ConfigurePr
  instance
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=523972:523973

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 13 2018

Components: 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.
Project Member

Comment 2 by ClusterFuzz, Mar 13 2018

Labels: Test-Predator-Auto-Owner
Owner: scottchen@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/62d0093b891fa483449513db827aee7b36760e0c (MD Extensions: eliminate lags when clicking between errors in the error console.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Labels: Test-Predator-Wrong-CLs
The CL is purely a WebUI change and did not touch anything mojo (or even C++) related.
Owner: ----
Status: Untriaged (was: Assigned)
Cc: brajkumar@chromium.org
Labels: -Pri-1 M-66 Pri-2
Owner: roc...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "interface_ptr_state.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/7ccd5748af65f98edbb5fbd44e60b7e61f8cec3f

rockot@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Comment 6 by roc...@chromium.org, Mar 28 2018

Mergedinto: 810595
Status: Duplicate (was: Assigned)
Project Member

Comment 7 by ClusterFuzz, Apr 2 2018

ClusterFuzz has detected this issue as fixed in range 547423:547424.

Detailed report: https://clusterfuzz.com/testcase?key=5725727119638528

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  mojo::internal::InterfacePtrStateBase::InitializeEndpointClient
  mojo::internal::InterfacePtrState<ukm::mojom::UkmRecorderInterface>::ConfigurePr
  instance
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=523972:523973
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=547423:547424

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

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

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

Sign in to add a comment