Memory Leak
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14.4k
- Forks
- 752
- Avg merge
- 10d 14h
- Merged PRs (30d)
- 1
Description
I often use a snippet tool (Greenshot) to quickly copy a part of a picture before sending it to someone else. When I do this with a picture open in ImageGlass, it causes a memory leak. I suspect it's caused by the combination of the keys. It happens only with ImageGlass, so I'm certain it's not a problem caused by other software.
I press Ctrl + print screen to capture a snippet, and right away, I have a huge memory leak that consumes 98% of my RAM.
I recently turned off copying multiple pictures in the ImageGlass setting. I doubt it's a factor, but I thought I would include it just in case.
System information
- Windows OS version: 10
- ImageGlass version: 9.2.0.1208
- ImageGlass release: Classic
To Reproduce
Steps to reproduce the behavior:
- Disable copying multiple images at once.
- Open an image in ImageGlass
- Press ctrl + print screen
Actual behavior
Memory leak
Expected behavior
No memory leak
Screenshots / Video / Sample image file
Additional context
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
No source file or test is named. First reproduce the leak on Windows 10 with ImageGlass 9.2.0.1208 by opening an image, disabling multiple-image copying, and pressing Ctrl+Print Screen with Greenshot; trace that interaction and consider the issue done when memory no longer rises to consume the system's RAM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100