https://bugs.kde.org/show_bug.cgi?id=491701
Dmitry Kazakov <dimul...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dimul...@gmail.com
--- Comment #1 from Dmitry Kazakov <dimul...@gmail.com> ---
Hi, Bugalt!
tldr; please attach the %localappdata%\krita-sysinfo.log and
%localappdata%\krita.log files to the bugreport and try to switch between Angle
and OpenGL renderers.
The topic of memory consumption is really complicated. The amount of memory
limit one sets in the preferences is related only to actual "image data" used
in Krita, i.e. layers, projections and so on. On the top of that, Krita has a
lot "not-accounted" memory, like opengl textures, transfer buffers, animation
cache and so on. It means that the amount of memory actually consumed by Krita
will always be higher than set in the preferences. And the slider in the status
bar gives only a rough estimation of the memory that the image consumes. It is
intentionally made rather pessimistic, i.e. it almost always shows higher
values than image consumes on real hardware. Just for the sake of efficiency.
Could you answer a few questions for me:
1) Does your image has animation?
2) Do you use 'on-disk-frames-cache' or 'in-memory-frame-cache'?
(Preferences->Performance->Animation)
3) What are the dimensions of the image (and the amount of frames if it is
animated)?
The backtrace looks rather weird. It shows that Krita crashes in some
openGL-related code. Which might be caused by a real out-of-memory condition or
just some other unrelated bug.
--
You are receiving this mail because:
You are watching all bug changes.
