Re-initialize autograd engine in child processes#4158
Merged
Conversation
soumith
approved these changes
Dec 13, 2017
apaszke
reviewed
Dec 13, 2017
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
The autograd engine uses threads for backwards. These don't exist after forks and they were not being re-initialized because the Engine::start_threads_flag was already set. This re-initializes the engine in child processes, which will cause it to re-create threads when backwards() is called in the child process. Note that we only attempt to handle the common case where fork() is called while the backwards threads are idle. Fixes pytorch#3966
cb5a95d to
0208a8c
Compare
apaszke
reviewed
Dec 16, 2017
| static bool _reinitialize_engine = false; | ||
|
|
||
| static void _maybe_reinitialize_engine_after_fork() { | ||
| // This is "probably" thread-safe because the flag is set in a fork handler |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
laurentdupin
pushed a commit
to laurentdupin/pytorch
that referenced
this pull request
Apr 24, 2026
* Re-initialize autograd engine in child processes The autograd engine uses threads for backwards. These don't exist after forks and they were not being re-initialized because the Engine::start_threads_flag was already set. This re-initializes the engine in child processes, which will cause it to re-create threads when backwards() is called in the child process. Note that we only attempt to handle the common case where fork() is called while the backwards threads are idle. Fixes pytorch#3966 * Avoid non-async-signal-safe functions in fork handler
This file contains hidden or 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
3 participants
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.
The autograd engine uses threads for backwards. These don't exist after
forks and they were not being re-initialized because the
Engine::start_threads_flag was already set. This re-initializes the
engine in child processes, which will cause it to re-create threads when
backwards() is called in the child process.
Note that we only attempt to handle the common case where fork() is
called while the backwards threads are idle.
Fixes #3966