PSA: Change to chrome.alarms API
94 views
Skip to first unread message
Oliver Dunk
Jun 9, 2023, 6:09:32 AM6/9/23
to Chromium Extensions
Hi everyone,
In M117, we are planning to limit the number of active alarms in an extension to 500. We are introducing this limit to address some performance issues we suspect are being caused by extensions that create an excessive number of alarms. We believe based on our data that this limit is high enough that it should not be hit by extensions in any use cases we are aware of.
If an extension attempts to create an alarm once this limit has been reached, chrome.alarms.create() will fail, setting chrome.runtime.lastError when using callbacks or rejecting if using a promise. When a non-repeating alarm fires, it will be automatically removed allowing additional alarms to be created.
If you have any concerns, please do let us know.
Thanks,
Oliver on behalf of Chrome Extensions DevRel
In M117, we are planning to limit the number of active alarms in an extension to 500. We are introducing this limit to address some performance issues we suspect are being caused by extensions that create an excessive number of alarms. We believe based on our data that this limit is high enough that it should not be hit by extensions in any use cases we are aware of.
If an extension attempts to create an alarm once this limit has been reached, chrome.alarms.create() will fail, setting chrome.runtime.lastError when using callbacks or rejecting if using a promise. When a non-repeating alarm fires, it will be automatically removed allowing additional alarms to be created.
If you have any concerns, please do let us know.
Thanks,
Oliver on behalf of Chrome Extensions DevRel
Reply all
Reply to author
Forward
0 new messages