Merge lp:~gue5t/midori/tabby-leaks into lp:midori
Proposed by
gue5t gue5t
Status: | Merged |
---|---|
Approved by: | André Stösel |
Approved revision: | 6676 |
Merged at revision: | 6678 |
Proposed branch: | lp:~gue5t/midori/tabby-leaks |
Merge into: | lp:midori |
Diff against target: |
163 lines (+44/-17) 1 file modified
extensions/tabby.vala (+44/-17) |
To merge this branch: | bzr merge lp:~gue5t/midori/tabby-leaks |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
André Stösel | Approve | ||
Review via email: mp+216810@code.launchpad.net |
Commit message
Fix leaks of two references to the MidoriApp in Tabby
Description of the change
Tabby seems to assume it will never be deactivated, which is an inherently leaky philosophy. This nulls out at least the two fields that hold references to the MidoriApp when Tabby is (theoretically) deactivated.
To post a comment you must log in.
Well, this will most likely break things if some event (which is handled by tabby) is triggered after deactivated is called. Yes, you are right, tabby assumes it is never deactivated, but if we change it, we should do it the right way.