(*** This bug was imported into bugs.kde.org ***) Package: konq-e Version: KDE 2.2.0 CVS/CVSup/Snapshot Severity: normal Installed from: Compiled sources Compiler: gcc OS: Linux OS/Compiler notes: arm linux on ipaq When viewing large (1Meg+) jpegs in konq-e on the ipaq it hangs and seems to hang the rest of qpe too. I think this is because it uses all the memory and has nothing to swap to. Perhaps it could deal more gracefully with OOM errors or perhaps a fixed upper limit to the amount that can be used in decoding a jpeg should be set. AFAIK there is nothing in the jpeg spec that precludes a small footprint decoder. This is quite a common situation as I am trying to use it on the ipaq to look at jpgs from a digital camera CF card. I also tried it out over http with the same pictures. It works with smaller jpeg images. (Submitted via bugs.kde.org)
When opening ~1Mb jpgs using the khtml widget my program or using Konqueror, it uses several hundred megs of memory to do so. Example files can be provided. RedHat 8.0, GCC 3.2 KDE 3.1 Beta 2 - built from source
*** Bug 26314 has been marked as a duplicate of this bug. ***
can confirm this. On kde 3.1.x memory consumption jump from 20Mb to 200Mb and increase each time the image is refresed. on kde 3.2, you no longer this so high memory consumption increase, but at each refresh it consumes more and more memory and this could lead to a crash of tghe entire system. Both X and kde process memory usage increase ( the biggest and fastest part for X ) test case : http://linux-wizard.tuxfamily.org/bugs/test4.html and http://linux-wizard.tuxfamily.org/bugs/images/MarPers2.jpg
*** This bug has been marked as a duplicate of 39693 ***