-
Notifications
You must be signed in to change notification settings - Fork 205
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
Break retain cycles and fix memory leaks #224
base: master
Are you sure you want to change the base?
Conversation
…efer top level elements.
That should have been all retain cycles now. Finally the git repository gets deallocated after the window is closed.
Sure. I was careful to use |
Can anyone verify on 10.7? |
Is 10.7 still relevant? Seems nobody here is using that anymore to test this. It is still very important to break those retain cycles so things get properly released. Not just because of memory.
Doesn't work as some pack-index-files are still open. |
10.7 and 10.8 each have roughly half the market share of 10.9; so dropping 10.7 is potentially 25% of users capable of running the current version. Weather that is relevant is debatable, but given the voracity with which bugs are reported when compatibility is broken, I'm leaning toward yes - however I have long said that 10.7 support in GitX won't be around forever unless somebody actually volunteers to maintain it. The time is coming, I think it may be basically after the next round of bug fixes. |
Conflicts: Classes/git/PBGitRepository.m
I should note: I like these changes. |
Fix exception when dragging files in the unstaged and staged changes table views
Added __weak and __unsafe_unretained at the appropriate places to break all retain cycles. So finally the git repository gets dealloced when the window is closed.