Page 1 of 1

Summary Images memory limit?

Posted: Sat Oct 05, 2013 7:59 am
by zxtunes.com
I load about 9,000 images, a total volumes of 1.2Gb.
Pictures are small (256x170px)
Windwows x64. Have 8 gigabytes of memory on computer.

Images are loaded and there is no error. However, when the first call StartDrawing (ScreenOutput) I get NULL.
I use full screen app.

I checked this notebook X86 and 1.5 gigabytes of memory.

The result is completely identical. What is surprising.

On the first computer built-in video card.
On a laptop with a discrete 256mb.

In what could be the problem?

PB5.2

Re: Summary Images memory limit?

Posted: Sat Oct 05, 2013 9:06 am
by Danilo
zxtunes.com wrote:However, when the first call StartDrawing (ScreenOutput) I get NULL.
Search: [ ScreenOutput null ]

- [PB5.20b8] ScreenOutput() does not work with InitEngine3D()
- Unable to draw to screen with engine3D
- Problem with StartDrawing(ScreenOutput())
- many more ...

Re: Summary Images memory limit?

Posted: Sun Oct 06, 2013 6:41 pm
by zxtunes.com
I not use Engine 3D. :oops:

Re: Summary Images memory limit?

Posted: Mon Oct 07, 2013 1:38 am
by Demivec
Did you make a typo, it should be:

Code: Select all

StartDrawing(ScreenOutput())

Re: Summary Images memory limit?

Posted: Mon Oct 07, 2013 9:36 am
by zxtunes.com
This is not funny. :o

Talk about the work program.

OK. I upload full source package: https://dl.dropboxusercontent.com/u/643 ... Mapper.zip (PB 5.2 need)

This program is needed for live shows, which I do sometimes with friends musicians.

At that time we had a banner 2.5x1.8 meters with a band logo .
In the center was a circle , where the output video. The remaining elements of the picture simply is highlighted in white.

Since it is not possible to install the projector exactly parallel to the screen , we had to make such a program.

The picture is divided into polygons which can be deformed independently . It turned out that they seem to glow .

The problem is that if you load memory images more than 1.2 years we get NULL on first StartDrawing(ScreenOutput()).
And it does not depend on the amount of RAM on your computer.

I believe that it is a bug PureBasic.
I checked on 3 different computers.

You can check this for yourself:

# number_videos = 30; 30 OK, 40 CRASH

Image