Summary: | Duplicate layer fills memory | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | SirPigeonz <GBirdboy> |
Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | cberger, dimula73, halla |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
SirPigeonz
2010-04-11 13:45:59 UTC
Yes currently, the full history of a paint layer is duplicated with the layer (and if the newly created layer is never edited, it is not purged). Ew. That cannot serve any useful purpose, can it? I don't know, I wanted to ask Dmitry about that. Well, i haven't tested it yet, but i guess this is the pooler preallocating tiles for future use. This is quite logical, especially when you are going to edit newly created (or source) layer. It is the common case, i guess. Though it could be quite cool feature for preallocated tiles to decay with the time. And i have to check about "the full history"... BUGDAY SVN commit 1165938 by dkazakov: Do not save the history of the cloned data manager. After a small discussion we decided there is no usecase for it. BUG:234038 M +4 -2 kis_tiled_data_manager.cc WebSVN link: http://websvn.kde.org/?view=rev&revision=1165938 |