-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screenshot severe memory leak #7
Comments
Thanks, Someone else pointed this out also, I just didn't have time to address it I plan to do some major overhauls of the project in the coming months and Cheers, On Wednesday, 15 January 2014, Remco Ros wrote:
|
Hey,
I don't know if you're still active on this project, but I have been playing with your code and found a severe memory leak.
The Screenshot (MarshalByRefObject) object is never released and it doesn't implement IDisposable.
If capturing a lot of screenshots, memory in the target process keeps growing.
In my case, this resulted in a OOM exception after ~30 seconds of getting consecutive screenshots.
Fix is simple, implement IDisposable, and call RemotingServices.Disconnect(this).
Then, make sure to call Dispose (or the using() construct) in the client application.
Hope that helps.
The text was updated successfully, but these errors were encountered: