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

issue #14

Open
nicolequist opened this issue Dec 5, 2015 · 0 comments
Open

issue #14

nicolequist opened this issue Dec 5, 2015 · 0 comments

Comments

@nicolequist
Copy link

Hi,

It is a cool library - great work!

However, we were using FBBitmapFont/View repeatedly [i.e. changing the text] and it is causing very large spike in memory - suddenly it grows to 50MB, 100MB and 200MB before it is killed by iOS.

  1. We have tested a few times and narrowed it down to this component. It happens very frequently if you change size of text and adjust the number of padding dots so it is centered.
  2. I've looked at Instruments and it is showing very huge single allocations [39MB, etc] with many CG calls.
  3. I've looked at the drawRect code and found a similar post here:
    http://stackoverflow.com/questions/19326551/sudden-memory-spike-with-cgcontextfillrect
    Most likely something like this is going on, but I am not a CoreGraphics expert.
  4. I also tested for potential UIGraphicsGetImageFromCurrentImageContext leak but it doesn't help:
    @autoreleasepool {
    per
    http://stackoverflow.com/questions/5121120/uigraphicsgetimagefromcurrentimagecontext-memory-leak-pdf-previews
    and ensure it runs on main thread
    per
    http://stackoverflow.com/questions/11582223/ios-ensure-execution-on-main-thread

Thanks in advance if you can look into it. Is a nice library.
Nicole

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

No branches or pull requests

1 participant