New issue
Advanced search Search tips

Issue 728299 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 739505
Owner: ----
Closed: Aug 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , iOS , All , Chrome , Mac
Pri: 3
Type: Task



Sign in to add a comment

Remove tracked_objects::ThreadData::EnsureCleanupWasCalled method.

Project Member Reported by michaeldo@chromium.org, May 31 2017

Issue description

This method was added more than 5 years ago to fix  crbug.com/103209  but the contained check has never been executed and the bug has been marked as fixed.

This call simply clutters client code and raises questions about why hardcoded thread counts exist. Especially because the code isn't executed and the value |4| isn't documented for existing callers.

We should remove this method and stop internally tracking |cleanup_count_|.
 
Owner: michaeldo@chromium.org
Status: Assigned (was: Untriaged)
Labels: -OS-Fuchsia
Cc: -michaeldo@chromium.org
Components: Internals
Owner: ----
Status: Untriaged (was: Assigned)

Comment 4 by jif@chromium.org, Jul 21 2017

Owner: jar@chromium.org
Status: Assigned (was: Untriaged)
Cc: thakis@chromium.org
Owner: ----
Status: Available (was: Assigned)
Project Member

Comment 6 by sheriffbot@chromium.org, Aug 27

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Mergedinto: 739505
Status: Duplicate (was: Untriaged)
This has now already been removed as part of  crbug.com/739505 .

Sign in to add a comment