Skip to content

Conversation

ioanatflowcrypt
Copy link
Collaborator

@ioanatflowcrypt ioanatflowcrypt commented Jul 31, 2025

This PR fixed alarm limit issue and service worker window issue

close #6051 // if this PR closes an issue


Tests (delete all except exactly one):

  • Does not need tests (refactor only, docs or internal changes)

To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

  • addresses the issue it closes (if any)
  • code is readable and understandable
  • is accompanied with tests, or tests are not needed
  • is free of vulnerabilities
  • is documented clearly and usefully, or doesn't need documentation

@ioanatflowcrypt ioanatflowcrypt marked this pull request as ready for review July 31, 2025 05:00
@ioanatflowcrypt
Copy link
Collaborator Author

ioanatflowcrypt commented Jul 31, 2025

@sosnovsky Could you update assignes as per priority?

I'm currently working on #5945 though

let db: IDBDatabase;
let storage: GlobalStoreDict;
const inMemoryStore = new ExpirationCache<string>('in_memory_store', 4 * 60 * 60 * 1000); // 4 hours
await BrowserMsg.guardAlarmFlood();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about just doing await chrome.alarms.clearAll() here? (without checking for alarms count in separate function)
I think reported case happens only for users who previously had more than 500 alarms when we were using random values in alarm names. this way we'll just remove all these unneeded alarms, and similar errors won't appear in the future.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed—this is simpler, as there are no saved critical alarms impacting current functionality.

Copy link
Collaborator

@sosnovsky sosnovsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@sosnovsky sosnovsky enabled auto-merge (squash) August 4, 2025 13:16
@sosnovsky sosnovsky merged commit b78fd08 into master Aug 4, 2025
11 checks passed
@sosnovsky sosnovsky deleted the 6051-error-an-extension-cannot-have-more-than-500-active-alarms branch August 4, 2025 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error: An extension cannot have more than 500 active alarms

2 participants