Merge lp:~agateau/unity-2d/dash-fork-on-close into lp:unity-2d/3.0
Proposed by
Aurélien Gâteau
Status: | Rejected | ||||
---|---|---|---|---|---|
Rejected by: | Florian Boucault | ||||
Proposed branch: | lp:~agateau/unity-2d/dash-fork-on-close | ||||
Merge into: | lp:unity-2d/3.0 | ||||
Diff against target: |
66 lines (+34/-2) 2 files modified
places/app/dashdeclarativeview.cpp (+2/-1) places/app/places.cpp (+32/-1) |
||||
To merge this branch: | bzr merge lp:~agateau/unity-2d/dash-fork-on-close | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Florian Boucault (community) | Disapprove | ||
Review via email: mp+56792@code.launchpad.net |
Description of the change
After running out of ideas to plug dash memory leaks, I came to try a workaround which can be summarized like this:
forever:
run the dash in a subprocess
when the user closes the view, exit the subprocess
It is definitely not a proper fix but it works well here. I believe the cost is acceptable: ld shouldn't load the libraries again so forking should remain fast, but it would need to be tested on lower-end machines.
To post a comment you must log in.
Unmerged revisions
- 519. By Aurélien Gâteau
-
Do not fork endlessly when X goes down
- 518. By Aurélien Gâteau
-
[dash] Work around memory leaks by running the application in a subprocess
See comments in places.cpp
Fix was committed to Qt4. This workaround is not needed anymore.