Hi Deakcor,
Thank you for responding and releasing the patch so quickly. I updated the Steam version to PixelOver 0.19.1.1 and continued working with the same project and 896×1344 RGB image.
The image-format error from my original report does not appear in the new session log. Thank you for fixing that.
The memory attributed to PixelOver still rises when I draw or erase. It was about 353 MB just after launch, before opening the project; after approximately 38 minutes of work, Activity Monitor showed 9.09 GB. The Mac remained responsive, memory pressure was green, and disk swap was zero. A later vmmap capture from the same running process reported a 10.5 GB footprint, including 4.5 GB of owned unmapped (graphics) regions.
I also noticed repeated Condition "idx < 0" is true errors in the new log, often near undo activity. I don’t know whether they are related to the rising memory figure.
Both screenshots, the full new session log, and the vmmap output are in this folder: https://drive.google.com/drive/folders/1CqY2Ggl2U71wo_UFst4EGhtgVOMdy9lY
Could you take another look at what is being retained during drawing and erasing?
