https://bugs.kde.org/show_bug.cgi?id=412740
b...@fastmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |b...@fastmail.com
--- Comment #5 from b...@fastmail.com ---
(In reply to wolthera from comment #4)
> I haven't seen an out-of-memory crash myself, and I think it's due to the
> pooling applied to Krita, as following the code trail leads to a 'delete
> later' type of object deletion.
Any objects that are created in a python script will only be freed when the
script ends AFAIK. In the case of an extension, it is always running, so it
continues to increase memory until Krita is closed.
This is easily reproducible with any extension/script that does
'Krita.openDocument()' and 'Document.close()' repeatedly on files in a
directory.
Running 'gc.collect()' or 'del <object>' in python doesn't seem to do anything.
Would a solution be to add a call to qt 'processEvents()' in something like
'Document.close()'? Seems like it would be a bad idea to force deletion (if
it's even possible) if it wasn't limited to python scripting.
--
You are receiving this mail because:
You are watching all bug changes.
