New issue
Advanced search Search tips

Issue 808922 link

Starred by 2 users
Status: WontFix
Owner:
nhiroki@chromium.org
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Direct-leak in content::WebServiceWorkerRegistrationImpl::CreateForServiceWorkerGlobalScope

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

Fuzzer: inferno_twister
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  content::WebServiceWorkerRegistrationImpl::CreateForServiceWorkerGlobalScope
  content::ServiceWorkerProviderContext::TakeRegistrationForServiceWorkerGlobalSco
  content::ServiceWorkerContextClient::WorkerContextStarted
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=524645:524646

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

Additional requirements: Requires HTTP

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 5 2018

Labels: Test-Predator-Auto-Owner
Owner: nhiroki@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/83f4deb951699e8ef8c1f7432ede75ac5074139b (Worker: Separate classic script evaluation from worker thread initialization).

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

Comment 2 by ClusterFuzz, Feb 5 2018

Components: Blink>ServiceWorker
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 3 by falken@chromium.org, Feb 5 2018

Labels: -Pri-2 Pri-1
Status: Untriaged (was: Assigned)
Hmm the blame CL looks plausible. Setting Untriaged to flag this.

Comment 4 by shimazu@chromium.org, Feb 9 2018

Cc: nhiroki@chromium.org
Owner: shimazu@chromium.org
Status: Assigned (was: Untriaged)
Blink-worker bug triaging. Assigned to shimazu@ for further investigation.

Comment 5 by falken@chromium.org, Feb 14 2018

Labels: -Type-Bug Type-Bug-Regression

Comment 6 Deleted

Comment 7 by shimazu@chromium.org, Feb 16 2018

Cc: -nhiroki@chromium.org
Owner: nhiroki@chromium.org
(blink-worker triaging) let's assign back to nhiroki@.
Project Member

Comment 8 by ClusterFuzz, Feb 19 2018

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6228060874211328 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