ruby-concurrency / ruby-concurrency/concurrent-ruby
[REDIRECT] Segfault on Ruby 3.3.0 on linux-aarch64? See https://bugs.ruby-lang.org/issues/20085
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.8k
- Forks
- 420
- Avg merge
- 20h 45m
- Merged PRs (30d)
- 4
Description
See https://bugs.ruby-lang.org/issues/20085
This is not a concurrent-ruby issue, so please do not file more issues about this.
Any segfault when not using concurrent-ruby-ext (the native extension) cannot be a bug in concurrent-ruby, but a bug in CRuby or in another native extension.
Duplicates: #1020 #1022
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
Start with bugs.ruby-lang.org/issues/20085, which this issue identifies as the relevant report, and review the duplicate issues #1020 and #1022. No concurrent-ruby file, test, or change is identified; the issue states that segfaults outside concurrent-ruby-ext belong to CRuby or another native extension.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100