New issue
Advanced search Search tips

Issue 613798 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

chrome.alarms triggering 10k+ times in a row, high cpu usage

Reported by tapa...@gmail.com, May 21 2016

Issue description

UserAgent: 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.
 
chbug.zip
632 bytes Download
Project Member

Comment 1 by sheriffbot@chromium.org, May 22 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment