Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pypy
pypy
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 584
    • Issues 584
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • PyPy
  • pypypypy
  • Issues
  • #3372

Closed
Open
Opened Jan 01, 2021 by Alex Orange@crazycastaDeveloper

multiprocessing.queues.Queue leaks pipes under certain conditions (CPython issue42752)

In writing a test for #3365 I noticed there's a bit of a problem with multiprocessor.queues.Queue. The trouble is if you don't actually put anything in the Queue (say for instance you're only using it to receive in the main process) the close method won't actually lead to the write pipe closing. Since the Queue is buffer and uses a thread, the closing of the write pipe is not exactly trivial. Branch py3_7_mp_queue_close_fix is my suggested fix.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pypy/pypy#3372