On 10/08/2009 21:46, Pavel Sanda wrote:
Abdelrazak Younes wrote:
Very intricate!
The problem is not coming from Qt but from our own caching mechanism which
is heavy and is redundant with Qt own caching system. Last time I tried to
clean up this mess I stopped at this issue with a big headache... The only
sane solution is to get rid of this complicated caching engine and to
rewrite everything with Qt only.
but my question is simpler now:
why should original_ = QImage(); release the memory as the comment above says?
if not what would be correct way of releasing it?
This code works and is not the problem. I don't remember the details but
the original image is also stored somewhere else in the graphics cache,
AFAIR.
Abdel.
