Error: An extension cannot have more than 500 active alarms

[martgil]

We received user reports where they are unable to send secure email as the following error prevents them from doing so. The user is using the latest version of Chrome browser, which would be 1.80.122 Chromium: 138.0.7204.157 (Official Build) (64-bit) at the time of writing this bug report.

Stack traces:

Error: An extension cannot have more than 500 active alarms. at <async> createIntervalAlarm (/extension/js/common/browser/browser-msg.ts:430:4) at <async> <anonymous> (/extension/js/service_worker/background.ts:21:2) ### Catch.reportErr calling stack ### # at Catch.formatExceptionForReport (chrome-extension://bnjglocicdkmhmoohhfkfkbbkejdhdgc/js/common/platform/catch.js:285:94) # at Catch.onErrorInternalHandler (chrome-extension://bnjglocicdkmhmoohhfkfkbbkejdhdgc/js/common/platform/catch.js:83:33) # at reportErr (chrome-extension://bnjglocicdkmhmoohhfkfkbbkejdhdgc/js/common/platform/catch.js:99:22) # # url: chrome-extension://bnjglocicdkmhmoohhfkfkbbkejdhdgc/js/service_worker/background.js # ######################

catch.js:70An extension cannot have more than 500 active alarms. Error: An extension cannot have more than 500 active alarms. at <async> createIntervalAlarm (/extension/js/common/browser/browser-msg.ts:430:4) at <async> <anonymous> (/extension/js/service_worker/background.ts:21:2)
catch.js:345ReferenceError: window is not defined at Url.parse (common.js:355:37) at Catch.doSendErrorToSharedTenantFes (catch.js:308:56) at Catch.onErrorInternalHandler (catch.js:91:20) at reportErr (catch.js:99:22)
doSendErrorToSharedTenantFes	@	catch.js:345

---

Reference:

https://mail.google.com/mail/u/human@flowcrypt.com/#inbox/FMfcgzQbgRkqtzvmFlKGFcxMkjScBvCR
https://mail.google.com/mail/u/human@flowcrypt.com/#archive/FMfcgzQbgcKjDBxnKKTzTbfHKMhqkSWQ

[sosnovsky]

@martgil do they have the latest version of FlowCrypt extension? Earlier this year Ioan implemented fix for this issue - 080a8a5, but maybe it still occurs in some situations.

[sosnovsky]

@ioanatflowcrypt I also noticed error message ReferenceError: window is not defined at Url.parse (common.js:355:37) at Catch.doSendErrorToSharedTenantFes (catch.js:308:56) at Catch.onErrorInternalHandler (catch.js:91:20) - it probably happens when error is reported from service worker, which doesn't have window property. Should use some placeholder URL in these cases, like https://mail.google.com

[ioanatflowcrypt]

Okay, got it.
Let me check.
Also @martgil Let me know if 500 active alarms issue happens in latest release

[martgil]

Hello team, I’ve just asked the reporter which version of the extension they’re running. That said, in most cases, they’re likely using the latest version due to Chrome’s automatic extension updates. I’ll share the exact version they’re running as soon as I have that information.

[martgil]

Hello @sosnovsky and @ioanatflowcrypt,

The user confirmed that they are using the latest version of the FlowCrypt browser extension.

[ioanatflowcrypt]

Hmm... I see
Thank you.

[martgil]

@sosnovsky @ioanatflowcrypt I can see that #6053 has been merged. Should this Github issue be marked that as completed and closed?

[sosnovsky]

@martgil yes, this one should be closed, mentioned PR has wrong issue number, thanks for noticing!

fixed in #6053

[martgil]

Thanks for the confirmation - this helps when providing user a feedback regarding the said issue.

Hopefully, it won’t resurface again once we’ve deployed it to production. In my usage, I haven’t observed it happening, though. Thanks.

[sosnovsky]

As a quick fix, they can try to reinstall extension - this way all existing alarms should be removed.