Memory leak with opened library
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
Start by reading the linked softbuffer issue and inspecting how tiny-xlib opens and releases the Xlib library. Check whether using ctor_lite::dtor! is appropriate for cleanup, and verify that the library is dropped without a memory leak when the process or relevant scope ends.
Written by the indexing model from the issue text.
Description
See https://github.com/rust-windowing/softbuffer/issues/252
Probably best to just use ctor_lite::dtor! to drop the library.
- Dominant language
- Rust
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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 rust-windowing/tiny-xlib
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
rust-windowing/tiny-xlib#16 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
rust-windowing/tiny-xlib#11 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Flaky CI Test Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in rust-windowing/tiny-xlib
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100