microsoft / microsoft/Windows-classic-samples
Magnifier Memory Leak
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5.7k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
MagnifierSample have a memory leak, as 8MB in full screen Mode with 1920x1080 resolution.
using memory usage profile in VS 2015 update 3 found the leak made bye this API MagSetWindowSource
Test on:
OS: win10 1909
GPU: NVIDIA 750
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 in the MagnifierSample entry point and reproduce the reported 8 MB growth in full-screen mode at 1920x1080 using the VS 2015 Update 3 memory profiler. Focus investigation on the mentioned MagSetWindowSource API call and compare memory usage across repeated updates. Done means the reported leak is isolated and a verified fix or confirmed API limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop-dev, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100