Allow mutex destruction
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.2k
- Forks
- 1.6k
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 13
Description
We don't have a mutex destruction API. Now that we allow "complete" arena destruction, there are locations that we call the OS-appropriate mutex-init function on, but never mutex destruction. This is fine most of the time, but can cause resource leaks on systems where mutex initialization requires resource allocation.
Contributor guide
No contributing guide indexed for this repository
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 by locating the OS-appropriate mutex initialization calls used during complete arena destruction and identify where matching cleanup is missing. Define and add the mutex destruction API for those paths, then verify that every initialized mutex is destroyed on systems where initialization allocates resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100