Bug 448288 - Krita 5.1.0 preaplpha issue : Weirdly filled blank space
Summary: Krita 5.1.0 preaplpha issue : Weirdly filled blank space
Status: RESOLVED DUPLICATE of bug 470842
Alias: None
Product: krita
Classification: Applications
Component: OpenGL Canvas (other bugs)
Version First Reported In: nightly build (please specify the git hash!)
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-11 23:28 UTC by stephen
Modified: 2023-06-21 12:25 UTC (History)
1 user (show)

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


Attachments
EmptySpaceFillIssue (157.09 KB, image/jpeg)
2022-01-11 23:28 UTC, stephen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description stephen 2022-01-11 23:28:58 UTC
Created attachment 145343 [details]
EmptySpaceFillIssue

SUMMARY
Krita git hash is 6db92d4.

There's like an issue with weirdly filled blank space which occurs in two cases.

STEPS TO REPRODUCE
Case 1 : Using Eraser on blank space
1.1. select an eraser brush or activate the erase mode 
1.2. erase in an already blank or empty area on a layer.

Case 2 : with opaque pixel data on a layer
2.1. Paint a little shape on a new layer
2.2. Flip the painted data left, right, up, down


OBSERVED RESULT
Case 1 : blank space is filled in the layer thumbnail
Case 2 : Krita "abnormally" fills the empty space travelled by the pixel data on the layer,
unnecessarily causing memory use. It result in a big rect shape with tiny pixel data in it.
Use transform tool to verify.


EXPECTED RESULT
Empty layer should be empty and not behave like it's filled, be it
on the layer thumbnail, or with the layer pixel data itself.

Warning : Might want to check whether it's happening with vector layers too.
Also this issue might've been hidden and present in many previous versions and current versions.


SOFTWARE/OS VERSIONS
Windows : 10 21H1
Comment 1 Halla Rempt 2023-06-21 12:25:29 UTC

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