-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Memory leaks or Instruments bad use/misunderstanding? #14
Comments
That was a bad code + misunderstanding of Instruments reports. Bad me. |
I'm experiencing the same issue in your SO post - what is the solution? Or are these cached items not a problem? |
The solution is to track and fix the memory leak, 99,94% chances that comes from your code... |
I don't doubt that I'm doing something wrong, I just can't seem to figure out what it is. Are there JSONKit examples somewhere? Was the issue that you had a matter of releasing the decoder object? This is what I am doing...
Are these autoreleased objects or do I need to handle releasing them? Confused...the leak report looks very similar to the one on Stack Overflow. Thanks for any help. |
JSONKit follows the standard Cocoa memory management conventions. In the example you provided, this means that the objects that are returned are The most likely cause of your problems is that you have inadvertently sent the |
... as for "examples", your snippet of code is pretty much all there is to JSONKit. The only other major function is turning
That's it. Which one you use depends on your needs- a That's all JSONKit does- it converts JSON in to |
Hi,
First of all, thanks a lot for your great work!
Could you please look at that SO question and tell us if those are leaks from JSONKit we are seeing or we are just noobs? :)
Feel free to contact me for more informations.
Vincent.
The text was updated successfully, but these errors were encountered: