-
Notifications
You must be signed in to change notification settings - Fork 48
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 not release #12
Comments
Could you try launching the picker more than once to see if it just keeps growing. Ideally profiling with Instruments. During the first launch is normal that some internal SDK caching/initialization takes place, thus consuming more memory. This may get released later or on low memory conditions automatically. As for memory leaks or circular retentions, I think I have checked many times in the past. |
I tried launching the picker more than once, it didn't keep growing. Thanks for your replying. 2015-01-22 9:21 GMT+08:00 Ernesto Rivera notifications@github.com:
|
What I usually try is to:
|
before open picker, the app use memory 30m
then open the picker, select one image,then the view push to the filter view
memory use increase to 110m
then click cancel button on the left navigation to dismiss controller view
memory use 100m
the 70m(100m - 30m) memory use will never release.
did some one also had this problem?
The text was updated successfully, but these errors were encountered: