This repository has been archived by the owner on Mar 3, 2025. It is now read-only.
Printing a warning when a browser instance is killed because of maxSu… #55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rvivalTime I think adding a warning when an instance is killed because it ran longer than the maxSurvivalTime would save people some time when debugging, because it's really not obvious to know what killed the process if you don't know the inner working of the library.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think adding a warning when an instance is killed because it ran longer than the maxSurvivalTime would save people some time when debugging, because it's really not obvious to know what killed the process if you don't know the inner working of the library.