Bug 386694 - Non-Destructive Performance Regression from 4.0 Pre-Alpha 1 to Pre-Alpha 2
Summary: Non-Destructive Performance Regression from 4.0 Pre-Alpha 1 to Pre-Alpha 2
Status: RESOLVED DUPLICATE of bug 407062
Alias: None
Product: krita
Classification: Applications
Component: Filters (show other bugs)
Version: 4.0 pre-alpha
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
Depends on:
Reported: 2017-11-09 19:49 UTC by reptillia39
Modified: 2019-05-02 08:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

The File. (3.68 MB, application/x-zip-compressed)
2017-11-09 19:51 UTC, reptillia39

Note You need to log in before you can comment on or make changes to this bug.
Description reptillia39 2017-11-09 19:49:14 UTC
Using a .KRA image made with 4.0 Pre-Alpha 1, the time it takes to filter it is almost instant, but with the latest Pre-Alpha, the performance regression is so severe that people who use non-destructive editing+instanced layers will no longer be able to work with later version of 4.0 on some images. For instances, the attached file. It is a small image taking 20.6 of memory space. In my 32 GB RAM computer, it should work nearly like an instance, and yet the filtering takes forever.
Comment 1 Halla Rempt 2017-11-09 19:50:56 UTC
What attached file?
Comment 2 reptillia39 2017-11-09 19:51:33 UTC
Created attachment 108766 [details]
The File.
Comment 3 reptillia39 2017-11-10 03:27:27 UTC
Wolthera mentioned to test the file without fill layer, but in a newly created document, fill layer seem to be the source of the performance regression. In that document, newly created color adjustment filter layer or Power/Slope/Output Filter Layer sometimes do cause performance regression. I believe the issues lies within fill layer, color adjustment, and the power/slope/output filter layer.
Comment 4 Halla Rempt 2017-11-26 15:00:06 UTC
Yes, I can confirm a performance regression. Opening the image in 4.0-prealpha.1 is fine; in git master, a20c53eea0c1548502b78a73879488a09a27844c, it starts an endless round of recalculations.
Comment 5 reptillia39 2018-02-04 04:46:23 UTC
Okay, I think this bug report can be closed as it's invalid, but I do think this bug report reveals a big issue that needs to be addressed at some point. If someone works with a bazillion filter layers/clone layers, then it can be difficult to track them, and to resolve this issue, there needs to be some way to reveal how the document works via a network to track those filters/clones easier. 

If the developers believe that there needs to be some way to track those layers down easier, I'll make the bug report if any developers asks me to do so if necessary, and let me know on the decision on that.
Comment 6 reptillia39 2018-02-04 04:53:31 UTC
Please disregard the above. That was meant for another report which has to do with a problem with many clone layers.
Comment 7 Halla Rempt 2019-05-02 08:40:44 UTC

*** This bug has been marked as a duplicate of bug 407062 ***