When repeating calling the function, the krunner process's memory consumption keeps getting larger and larger. The leak is gone when commenting out the function.
So, you closed the issue because the leak isn't in AppStream?
(AFAIK there is no memory leak, because I profiled this a lot last year, but on the other hand there's always a chance that one was introduced since the last manual analysis and asan didn't catch it automatically)
When repeating calling the function, the krunner process's memory consumption keeps getting larger and larger. The leak is gone when commenting out the function.
Heaptrack result: heaptrack.tar.gz
The text was updated successfully, but these errors were encountered: