Modules are not deallocated correctly if m_size = -1

Open
#50,732 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, python
Domain
backend

Research direction

Start with the attached test.c test case and the CPython interpreter-core code governing module deallocation when m_size is -1. Determine the expected module lifetime and reproduce the reported behavior; done means the test case demonstrates correct deallocation without regressions in the relevant interpreter tests.

Written by the indexing model from the issue text.

Description

interpreter-core type-bug
BPO 6483
Nosy @loewis, @pitrou
Files
  • test.c: Test case.
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = 'https://github.com/loewis'
closed_at = None
created_at = <Date 2009-07-14.12:03:53.395>
labels = ['interpreter-core', 'type-bug']
title = 'Modules are not deallocated correctly if m_size = -1'
updated_at = <Date 2014-02-03.19:22:30.501>
user = 'https://bugs.python.org/jak'

    bugs.python.org fields:

    activity = <Date 2014-02-03.19:22:30.501>
actor = 'Arfrever'
assignee = 'loewis'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2009-07-14.12:03:53.395>
creator = 'jak'
dependencies = []
files = ['14500']
hgrepos = []
issue_num = 6483
keywords = []
message_count = 5.0
messages = ['90514', '90535', '103700', '104161', '190085']
nosy_count = 4.0
nosy_names = ['loewis', 'pitrou', 'Arfrever', 'jak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue6483'
versions = ['Python 3.1', 'Python 3.2', 'Python 3.3', 'Python 3.4']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.