Mutlithread XML parsing cause segfault
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with the attached pyexpat_crash_multithread.py reproduction and inspect the pyexpat XML component it exercises. Run the script in a threaded setup to confirm the segfault, then trace the relevant parser behavior and add or update a regression test that demonstrates the corrected result without a crash.
Written by the indexing model from the issue text.
Description
| BPO | 17970 |
|---|---|
| Nosy | @amauryfa, @pitrou, @tiran, @alex, @iritkatriel |
| Files |
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 2013-05-13.13:52:38.896>
labels = ['expert-XML', '3.10', '3.9', 'type-crash', '3.11']
title = 'Mutlithread XML parsing cause segfault'
updated_at = <Date 2021-09-07.12:55:23.850>
user = 'https://bugs.python.org/mrDoctorWho0'
bugs.python.org fields:
activity = <Date 2021-09-07.12:55:23.850>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['XML']
creation = <Date 2013-05-13.13:52:38.896>
creator = 'mrDoctorWho0..'
dependencies = []
files = ['30250']
hgrepos = []
issue_num = 17970
keywords = []
message_count = 8.0
messages = ['189131', '189159', '189161', '189162', '189225', '189232', '189533', '401257']
nosy_count = 6.0
nosy_names = ['amaury.forgeotdarc', 'pitrou', 'christian.heimes', 'alex', 'mrDoctorWho0..', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue17970'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·