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

Reduce memory usage related to event handling on OS X #672

Closed
mantognini opened this Issue Jul 26, 2014 · 2 comments

Comments

Projects
None yet
1 participant
@mantognini
Member

mantognini commented Jul 26, 2014

Even though there is no actual leak, generating events (e.g. moving the mouse or typing on the keyboard) will increase the memory footprint of the application.

This is easily fixed by wrapping the while loop of -[SFApplication processEvent] into an autorelease pool.

The current internal API provided by AutoreleasePoolWrapper.{h,mm} needs a quick refactoring.

@mantognini mantognini added this to the 2.2 milestone Jul 26, 2014

@mantognini mantognini added bug labels Jul 26, 2014

@mantognini mantognini self-assigned this Jul 26, 2014

@mantognini

This comment has been minimized.

Show comment
Hide comment
@mantognini

mantognini Aug 3, 2014

Member

Note to myself: draining the pool after the event loop break the menu; sending a keyboard shortcut crash the app.

Member

mantognini commented Aug 3, 2014

Note to myself: draining the pool after the event loop break the menu; sending a keyboard shortcut crash the app.

@mantognini

This comment has been minimized.

Show comment
Hide comment
@mantognini

mantognini Sep 14, 2014

Member

The crash mentioned in my previous message was fixed with the last commit. Now this issue is superseded by PR #698.

Member

mantognini commented Sep 14, 2014

The crash mentioned in my previous message was fixed with the last commit. Now this issue is superseded by PR #698.

@mantognini mantognini closed this Sep 14, 2014

@mantognini mantognini removed their assignment Apr 30, 2015

@mantognini mantognini self-assigned this Feb 7, 2016

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