Move 'super-long post delayed task' warning to IncomingTaskQueue.

Move 'super-long post delayed task' warning to IncomingTaskQueue.

This is a follow-up based on TBR review comments made to this change:
https://codereview.chromium.org/873393004

This moves the warning message to a more-central location so that posting
delayed tasks from additional call points (eg., MessageLoopProxy) will be
checked.

BUG=450045
Committed: https://crrev.com/5d4e9ddd94d94e02c2ec008a3465305a1feb3c1e
Cr-Commit-Position: refs/heads/master@{#314392}

[miu, 2015-01-27 19:10:16]

Patchset #1 (id:1) has been deleted

[miu, 2015-01-28 19:30:30]

miu@chromium.org changed reviewers:
+ darin@chromium.org

[miu, 2015-01-28 19:30:30]

darin: PTAL.

This is a TBR follow-up on your comments from here:
https://codereview.chromium.org/873393004  See my last (post-commit) message
there where I respond to your comments.

This change causes a doubling of the number of warnings (DEBUG builds only),
which amounts to a total of about 16-ish.  They are all logged within the first
30 seconds of starting the browser.  The log messages don't seem to spam after
that under typical use of the browser.

[miu, 2015-01-28 19:33:44]

Here's an example from a Debug_x64 build on my dev desktop:

$ cat LAST_CHROME_LOG.txt | grep incoming_task_queue.cc
[7252:4136:0128/192648:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 86302118316 usec from here:
policy::PolicyStatisticsCollector::ScheduleUpdate@d:\src\chromium\src\components\policy\core\common\policy_statistics_collector.cc:91
[7252:4136:0128/192648:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 86362105000 usec from here:
web_resource::WebResourceService::ScheduleFetch@d:\src\chromium\src\components\web_resource\web_resource_service.cc:88
[7252:4136:0128/192648:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 21507126000 usec from here:
web_resource::WebResourceService::ScheduleFetch@d:\src\chromium\src\components\web_resource\web_resource_service.cc:88
[7252:4136:0128/192648:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 9210305133245995410 usec from here:
gcm::GCMAccountTracker::ScheduleReportTokens@d:\src\chromium\src\chrome\browser\services\gcm\gcm_account_tracker.cc:88
[7252:4136:0128/192648:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 86400000000 usec from here:
HotwordAudioHistoryHandler::UpdateAudioHistoryState@d:\src\chromium\src\chrome\browser\search\hotword_audio_history_handler.cc:41
[7252:9792:0128/192649:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 3600000000 usec from here:
storage::QuotaManager::DidInitialize@d:\src\chromium\src\storage\browser\quota\quota_manager.cc:1553
[7252:9792:0128/192649:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 3600000000 usec from here:
storage::QuotaTemporaryStorageEvictor::Start@d:\src\chromium\src\storage\browser\quota\quota_temporary_storage_evictor.cc:144
[7252:9792:0128/192649:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 1800000000 usec from here:
storage::QuotaTemporaryStorageEvictor::StartEvictionTimerWithDelay@d:\src\chromium\src\storage\browser\quota\quota_temporary_storage_evictor.cc:151
[7252:4136:0128/192649:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 86400000000 usec from here:
extensions::QuotaService::QuotaService@d:\src\chromium\src\extensions\browser\quota_service.cc:27
[7252:4136:0128/192649:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 21600000000 usec from here:
BrowserProcessImpl::StartAutoupdateTimer@d:\src\chromium\src\chrome\browser\browser_process_impl.cc:845
[7252:4136:0128/192649:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 18000000000 usec from here:
chrome_variations::VariationsRequestScheduler::Start@d:\src\chromium\src\chrome\browser\metrics\variations\variations_request_scheduler.cc:20
[7252:4136:0128/192649:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 3600000000 usec from here:
history::TopSitesImpl::RestartQueryForTopSitesTimer@d:\src\chromium\src\chrome\browser\history\top_sites_impl.cc:900
[7252:4136:0128/192649:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 7200000000 usec from here:
UpgradeDetectorImpl::StartTimerForUpgradeCheck@d:\src\chromium\src\chrome\browser\upgrade_detector_impl.cc:344
[7252:4136:0128/192650:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 3600000000 usec from here:
data_reduction_proxy::DataReductionProxyStatisticsPrefs::DelayedWritePrefs@d:\src\chromium\src\components\data_reduction_proxy\core\browser\data_reduction_proxy_statistics_prefs.cc:156
[7252:4136:0128/192651:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 3527271700 usec from here:
extensions::AlarmManager::SetNextPollTime@d:\src\chromium\src\chrome\browser\extensions\api\alarms\alarm_manager.cc:318
[7252:4136:0128/192651:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 1727540903 usec from here:
extensions::AlarmManager::SetNextPollTime@d:\src\chromium\src\chrome\browser\extensions\api\alarms\alarm_manager.cc:318
[7252:4136:0128/192659:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 691260000000 usec from here:
safe_browsing::ClientSideDetectionService::ScheduleFetchModel@d:\src\chromium\src\chrome\browser\safe_browsing\client_side_detection_service.cc:266
[7252:4136:0128/192703:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 1800000000 usec from here:
rappor::RapporService::ScheduleNextLogRotation@d:\src\chromium\src\components\rappor\rappor_service.cc:163
[7252:4136:0128/192704:WARNING:incoming_task_queue.cc(55)] Requesting super-long
task delay period of 3600000000 usec from here:
history::TopSitesImpl::RestartQueryForTopSitesTimer@d:\src\chromium\src\chrome\browser\history\top_sites_impl.cc:900

[miu, 2015-01-28 20:29:56]

Also, scottmg@ and I were discussing the threshold in https://crbug.com/450045. 
It seems the current threshold catches a lot of "between one hour and one day"
delayed tasks that are legitimate.  Do you think I should raise the threshold to
reduce logging spam?  If so, what should the threshold be?  30 days?

[miu, 2015-02-03 04:47:34]

darin: Friendly ping.

[darin (slow to review), 2015-02-03 18:30:58]

LGTM

(apologies for the delay)

[miu, 2015-02-03 18:57:49]

The CQ bit was checked by miu@chromium.org

[commit-bot: I haz the power, 2015-02-03 18:58:19]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/878033005/20001

[commit-bot: I haz the power, 2015-02-03 20:10:53]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2015-02-03 20:11:50]

Patchset 1 (id:??) landed as
https://crrev.com/5d4e9ddd94d94e02c2ec008a3465305a1feb3c1e
Cr-Commit-Position: refs/heads/master@{#314392}