memory leak in memMapIpc
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.6k
- Forks
- 2.4k
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
OS: Windows11
Platform: Visual Studio 2022 Debug X64
Version: NVIDIA-SMI 516.94 Driver Version: 516.94 CUDA Version: 11.7
In the sample memMapIPCDrv, seems like memory does not release to the OS (Both GPU memory and CPU memory) utile child process exit.
Is this a bug? or I miss some cleanup?
PS.
- I change
DATA_BUF_SIZEto 4G. - I move the
cuMemReleasein parent process ahead ofwaitProcess, and both child process and parent process pause just before callexit.
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 the Samples/3_CUDA_Features/memMapIPCDrv sample entry point and trace DATA_BUF_SIZE, cuMemRelease, and waitProcess in both processes. Reproduce the 4G Windows Debug X64 case, then compare resource lifetime through child and parent exit; done when the memory behavior is explained and the sample or issue guidance reflects the verified cleanup behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100