Skip to content
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 management #86

Open
GoogleCodeExporter opened this issue Feb 7, 2016 · 6 comments
Open

memory management #86

GoogleCodeExporter opened this issue Feb 7, 2016 · 6 comments

Comments

@GoogleCodeExporter
Copy link

use the app a few times or over the course of a couple of days, it will start 
acting weired, like 
closing out a uiwebview and going directly back to accounts screen
then the device itself will start acting strange (iPhone)

I checked with instruments and memory tools in Xcode and the app seems to have 
some memory 
leaks and some substantial memory usage at times - I am having difficulty 
tracking down the leaks 
but we need to make sure that it does not have memory leaks. Otherwise, it 
makes not only the app 
act improperly, but will also have an effect on the entire device even when the 
app is closed

Original issue reported on code.google.com by [email protected] on 12 Mar 2010 at 4:03

@GoogleCodeExporter
Copy link
Author

Leaks you have observed may be caused by leaks in freeware third party 
libraries used in yFrog.
For example we aware about leak in oAuth library but we can not fix it. 
Please read for more information:
http://code.google.com/p/oauth/issues/detail?id=128 

Original comment by [email protected] on 15 Mar 2010 at 5:06

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 16 Mar 2010 at 8:35

  • Added labels: Milestone-Release3.0

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 29 Mar 2010 at 10:19

  • Added labels: Priority-High
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

This is serious enough NOT to defer it but I am not able to reproduce it at the
moment. defer to the next release unless more information can be 

Original comment by [email protected] on 21 May 2010 at 7:23

@GoogleCodeExporter
Copy link
Author

... more information can be gathered to support that this is a more serious 
issue,
and cannot be deferred. 

Original comment by [email protected] on 21 May 2010 at 7:25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant