Memory leak with _responseData instance variable of EGOImageLoadConnection #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ariable. This was causing a memory leak in my application.
|
thx for this commit!! solved my leaks too |
|
Way Awesome! Man was that leaking! |
shnhrrsn
added a commit
that referenced
this pull request
Apr 30, 2011
Memory leak with _responseData instance variable of EGOImageLoadConnection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi guys,
My application was reporting a memory leak on Instruments until I finally tracked it down to the _responseData variable of EGOImageLoadConnection. It was not being released.
This commit just releases that variable on the dealloc method. It fixed the memory leak I had in my application.
Thanks for writing such a great library!