The python interpreter crashed with "_enter_buffered_busy"
Open
Nobody has claimed this yet.
interpreter-core
type-crash
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42717 |
|---|---|
| Nosy | @markshannon, @stestagg |
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 = None
closed_at = None
created_at = <Date 2020-12-22.10:25:03.254>
labels = ['interpreter-core', '3.10', 'type-crash']
title = 'The python interpreter crashed with "_enter_buffered_busy"'
updated_at = <Date 2021-01-18.11:40:55.491>
user = 'https://bugs.python.org/xxm'
bugs.python.org fields:
activity = <Date 2021-01-18.11:40:55.491>
actor = 'Mark.Shannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-12-22.10:25:03.254>
creator = 'xxm'
dependencies = []
files = []
hgrepos = []
issue_num = 42717
keywords = []
message_count = 9.0
messages = ['383582', '383609', '383628', '383913', '383953', '384007', '384045', '385172', '385191']
nosy_count = 3.0
nosy_names = ['Mark.Shannon', 'xxm', 'stestagg']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue42717'
versions = ['Python 3.10']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names no source files, tests, or reproduction steps. Start by reading the migrated BPO issue 42717 and its comment history to identify the failing interpreter path and how the crash can be reproduced; done would require a confirmed cause, a regression test, and a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100