Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • P Pyston
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Boxiang Sun
  • Pyston
  • Repository
You need to sign in or sign up before continuing.
  • Pyston
  • src
  • core
  • threading.cpp
Find file BlameHistoryPermalink
  • Kevin Modzelewski's avatar
    While investigating fork() behavior, found another threading bug · 51d65601
    Kevin Modzelewski authored Dec 16, 2014
    We weren't able to exit if we had a thread running in the background,
    since we released the GIL at the end of the C level main() and the
    background thread would start running again after all the data structures
    had been torn down.
    
    Now, just keep holding the GIL as we exit.
    51d65601
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7