Bug 397618 - undo sometimes erases whole layer chunk
Summary: undo sometimes erases whole layer chunk
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: General (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-19 11:30 UTC by kde
Modified: 2018-08-19 14:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
visual representation of error occuring (40.16 KB, image/png)
2018-08-19 11:30 UTC, kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2018-08-19 11:30:13 UTC
Created attachment 114494 [details]
visual representation of error occuring

I am using krita version 4.0.3 , but i was unable to specify that in the report field and since i rather finish my current work in a "stable" environment i have no way to test it for now in a newer versions. I am pretty sure it's something i have experienced in the previous versions, at least in 4.* branch.

I am working on a big canvas (4096x7016 px) and sometimes when i try to undo the stroke, what ends up happening is that i end up with missing rectangular "chunk" of a layer i'm working on, where the stroke was present (see attachment, where i have tried to visualize that. The cyan rectangle is not something that actually shows up on the canvas, it's just here to illustrate what i think ends up getting missing, since it's always a rectangular chunk around stroke). 

It might be happening when i use undo, while the document is autosaving, but it don't really have the reliable way to test that manually. 

My other guess is that it happens when i am running out of RAM and system starts using the swap for storage.

There are no errors that end up in stdout/stderr in console.
Comment 1 Halla Rempt 2018-08-19 14:03:55 UTC
You're unable to specify 4.0.3 in the report because that is so old we cannot accept reports for it anymore. Please update to 4.1.1.