| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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
| Back | FazBrowse Home | New Git URL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualityThis unconditionally resets TextIOWrapper's PyThreadMutex in the child, but the forking thread can still have a live guard on that same lock when fork() is called from code executed under the lock (for example, TextIOWrapper::write calls encoder.encode while holding self.lock(vm), and a custom encoder can call os.fork()). After this reset, that pre-fork guard will later drop and call unlock() on a mutex that was forcibly reinitialized, which can corrupt lock state or panic in parking_lot. Please guard this path so locks currently owned by the calling thread are not blindly reinitialized.
Useful? React with 👍 / 👎.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.