Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase dead message channel timeout #1162

Merged
merged 1 commit into from
Jun 5, 2024
Merged

Conversation

emaxx-google
Copy link
Collaborator

Consider a message channel dead only after 10 min of silence, regardless of Debug or Release build mode.

This should fix the observed rare event in Debug build, when communication between client extensions and Smart Card Connector was considered dead despite the pages staying alive seemingly. This problem is especially disruptive in the manifest v3 extension build mode, since closing message ports can lead to the termination of service workers.

Consider a message channel dead only after 10 min of silence, regardless
of Debug or Release build mode.

This should fix the observed rare event in Debug build, when
communication between client extensions and Smart Card Connector was
considered dead despite the pages staying alive seemingly.
@emaxx-google emaxx-google added this to In progress in Extension migration via automation May 13, 2024
Copy link

Continuous Integration: All tests passed.
C/C++ test coverage: 73.30% lines.

@emaxx-google emaxx-google merged commit 1bc5aa2 into main Jun 5, 2024
13 checks passed
Extension migration automation moved this from In progress to Done Jun 5, 2024
@emaxx-google emaxx-google deleted the mv3-ping-timeout branch June 5, 2024 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants