Meta-Issue: Mutli-threading leads to segfaults
- Vorherrschende Sprache
- Julia
- Sterne
- 1.5k
- Forks
- 186
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
This seems to be coming up quite often, in order to track this issue I took the liberty to create this meta-issue linking all other related issues I could find:
https://github.com/JuliaPy/PyCall.jl/issues/1095
https://github.com/JuliaPy/PyCall.jl/issues/1090
https://github.com/JuliaPy/PyCall.jl/issues/1088
https://github.com/JuliaPy/PyCall.jl/issues/1083
https://github.com/JuliaPy/PyCall.jl/issues/1078
https://github.com/JuliaPy/PyCall.jl/issues/1077
https://github.com/JuliaPy/PyCall.jl/issues/1072
Affected repos:
https://github.com/timholy/Revise.jl/issues/989
Possible also related (crashes/segfaults)
https://github.com/JuliaPy/PyCall.jl/issues/1082
https://github.com/JuliaPy/PyCall.jl/issues/1080
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Start by reviewing the linked PyCall.jl issues 1095, 1090, 1088, 1083, 1078, 1077, 1072, 1082, and 1080, plus the Revise.jl issue 989. Compare their multithreading-related crashes and reproduce the common failure before defining a focused fix or follow-up; done means the related reports are understood and the work is scoped beyond this meta-issue.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- julia, python
- Bereich
- backend
- Issue-Typ
- Bug
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 20/100