Corrupted display in low-memory conditions

[Maysoon88]

Hi,

I posted a thread before about Qt message out of memory when rotating device and this is the link of the thread:

http://discussion.forum.nokia.com/fo...237#post811237

And I mostly believed that it was a result of a memory leak !!! but I noticed that there is a bug on this link:

http://bugreports.qt.nokia.com/browse/QTBUG-11728

and I think its very close to my problem, so can anyone help, because till now I didn't find a solution for my "corrupted display" issue ??!!!

[danhicksbyron]

When you get into low memory situations then images begin to fail to draw. This can be due to a memory leak, or due to simply putting 10 pounds of "stuff" in a 5-pound bag.

The "bug" report is simply reporting a well-known "feechure".

[Maysoon88]

When you get into low memory situations then images begin to fail to draw. This can be due to a memory leak, or due to simply putting 10 pounds of "stuff" in a 5-pound bag.

The "bug" report is simply reporting a well-known "feechure".

Sorry but what does "putting 10 pounds of "stuff" in a 5-pound bag" mean? I didn't get it well

what could be the mistake in code???

[danhicksbyron]

It simply means too much stuff for the amount of heap you have -- sometimes you need to increase the heap size.

(In the America colloquialism a different word is used in place of "stuff".)

[Maysoon88]

It simply means too much stuff for the amount of heap you have -- sometimes you need to increase the heap size.

(In the America colloquialism a different word is used in place of "stuff".)

I see, but I increased heap size and that was useless!!!

[danhicksbyron]

Then either you've got WAY too much "stuff", or you have a storage leak.

A very common problem is loading large (eg, 3mb) images and then down-sizing them. You can get maybe 3 images loaded before things break.