In practice this is most likely only a leak on exit which does not
matter, but it makes using Valgrind etc impossible.
Details
Details
- Reviewers
davidedmundson - Group Reviewers
Plasma - Commits
- R104:ff717c0a9c4c: Do not leak all instances of QMLOutput when QMLScreen is destroyed
Diff Detail
Diff Detail
- Repository
- R104 KScreen
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
kcm/src/declarative/qmlscreen.cpp | ||
---|---|---|
96 | this should clear them already? |
kcm/src/declarative/qmlscreen.cpp | ||
---|---|---|
96 | parentItem is only visual parent, it doesn't communicate ownership |
Comment Actions
I also thought the call to setParentItem would clear the output. But as @broulik says it does not delete automatically. So is this good to go? Or should we make QMLScreen really a Qt Object parent of the outputs?