Fix error: Timeout: Did not receive an init message from worker after 10000ms #197
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A user had reported that their replay browser wasn't working, despite the correct paths being set. After looking at their logs it was clear that the
replayBrowser: Spawning worker: Donelog message was never received, and no errors were being thrown.After adding more error logs, we discovered the
Timeout: Did not receive an init message from worker after 10000mserror. This is peculiar since the user has incredibly good PC specs, so why initializing workers takes longer than 10s is extremely odd. Anyways, it turns out just increasing the timeout from the default 10s to 30s fixed the issue for them.