Version: (using KDE KDE 3.3.0) Installed from: Slackware Packages Compiler: gcc 3.3.4 OS: Linux When scanning a large (about 20) number of images (about 15-20 MB of uncompressed data each) one after another, memory usage (shown by the System Monitor applet) grows steadily with each scanned image (other tools show that it's kooka that allocating this memory). After about 20 images, kooka crashes (the machine has 384 MB RAM and 80 MB swap; unfortunately I don't have a backtrace from taht machine). After kooka dies, the memory in question is freed (which confirms that it was allocated by kooka).
Same problem over here. 512 MB RAM, 100 MB swap, Mustek ScanExpress 12000SP (SCSI) Installed from: Debian Packages (testing/Linux) Version: 0.44 (KDE 3.3.0)
Well, this is not really a bug. When kooka shows an image, the image data is left in memory. That is indicated by the icon in the gallery tree: Images that are not loaded into memory appear as a disk symbol, loaded images appear as a either color, bw or gray symbol. After having scanned 20 big images they are all loaded into memory. But they can be unloaded: clicking the right mouse button, you find a menu 'unload image' and that simply frees the memory. It also works for complete directories. Anyway some things remain: - there should be a limit of memory consumption. - the app should not crash
This is not always the case. I have 1gb ram and 1gb swap and kooka allocated almost all of it. (I run evilwm and a generally light system) I don't use the kooka gallery. I was scanning in and scp'ing the images from the kooka Scanimages directory to my server, then deleting them. Since they left the gallery as soon as the file was deleted I didn't worry about it. After scanning in many (!) documents, my computer went into a swapstorm until the kernel killed kooka. In that case, there is no mechanism for the user to free the memory.
I have similar problems after scanning of 5 to 10 files with an uncompressed of size about 400 - 500 MB each. But Kooka is not crashing then, it seems that it's doing it's job as expected. But the files are not saved any more. I continued scanning a pretty long time till I recognized it. Besides, I confirm, that there should be a limit for maximum memory usage. Even other applications have problems with the little memory left (e.g. exporting files to jpg in GIMP doesn't work). And I didn't find the right-mouse-button-menu "unload image", so I always have to close and reopen Kooka.
Thank you for the report, Michal. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!