chrome.alarms triggering 10k+ times in a row, high cpu usage
Reported by
tapa...@gmail.com,
May 21 2016
|
|
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0 Steps to reproduce the problem: 1. Unpack chbug.zip attach 2. "Load unpacked extension..." into chrome (in dev. mode) 3. Click "background page" of extension to inspect it in Developer Tools and open its console 4. Change local system clock to the previous day of the same month and click "Reload" extension link as fast as possible 5. About 10k (or more) "Reload" messages appear in console. Chrome also utilizes cpu a lot. What is the expected behavior? On each reload there is only one "Reload" message What went wrong? Alarm listener is executing before its "when" option WebStore page: Did this work before? N/A Chrome version: 51.0.2704.54 beta-m (64-bit) Channel: beta OS Version: 8.1 Flash Version: Shockwave Flash 21.0 r0 It is possible to reproduce this issue even without dev. mode, despite of the fact, that alarms is limited to trigger once in a minute. |
|
►
Sign in to add a comment |
|
Comment 1 by sheriffbot@chromium.org
, May 22 2017