Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Failed to open mutex on Windows

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
rust

Research direction

Start in src/locks/windows.rs at lines 65-70 and compare the mutex naming behavior with the linked Windows CreateMutex documentation. Reproduce the cross-process raw_sync and shared_memory case on Windows, then verify that the mutex opens successfully across processes.

Written by the indexing model from the issue text.

Description

While using raw_sync together with shared_memory works fine on Linux across processes on Windows I get a Failed to open mutex mutex_ID from https://github.com/elast0ny/raw_sync-rs/blob/master/src/locks/windows.rs#L65-L70

Taking a quick peek at the Windows API docs it seems like mutex object names might need Global\ as prefix to be available across processes

Source: https://docs.microsoft.com/en-us/windows/win32/api/synchapi/nf-synchapi-createmutexa

Dominant language
Rust
Stars
66
Forks
20
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elast0ny/raw_sync-rs

All issues in elast0ny/raw_sync-rs

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.