[KimDaBa] Reducing memory consumption

Jesper K. Pedersen blackie at blackie.dk
Sun Jan 16 20:29:26 CET 2005


On Sunday 16 January 2005 20:27, Robert L Krawitz wrote:
|    From: "Jesper K. Pedersen" <blackie at blackie.dk>
|    Date: Sun, 16 Jan 2005 20:20:51 +0100
|    Cc: kimdaba at klaralvdalens-datakonsult.se
|
|    On Sunday 16 January 2005 20:17, Robert L Krawitz wrote:
|    |    From: "Jesper K. Pedersen" <blackie at blackie.dk>
|    |    Date: Sun, 16 Jan 2005 20:09:30 +0100
|    |
|    |    I'm afraid that I can't apply this patch.  I need to detach
|    |    otherwise there might be a race condition between the two threads
|    |    for the reference counter for the QImage.  I changed the code so it
|    |    will detach right after putting the image in the ImageEvent, this
|    |    will hopefully resolve the issue, and will ensure that the image is
|    |    not copied an extra time when taken out of the event in the GUI
|    |    code.
|    |
|    | So that's still going to force a copy?  That's unfortunate, since it's
|    | a huge chunk of VM.  There's no way to lock the image?
|
|    I'm afraid not.  The problem is that the GUI thread and the image
|    loading thread might at the same time reduce the reference counter,
|    resulting in it being decrecaded one too little.
|
| It's not possible to lock the operations that might change the
| reference counter?
no.
This is in code that is out of my control.

As I said this will be resolved with Qt4 which are due this spring - perhaps 
even before KimDaBa 2.1 is due

-- 
Having trouble finding a given image in your collection containing
thousands of images?

http://ktown.kde.org/kimdaba might be the answer.



More information about the KimDaBa mailing list