Sorry your browser is not supported!

Im using ianm`s load queued item dll to load bitmaps into memory and after a while running (1hr+) windows will announce its expanding the swap file and then the program halts. Im loading a lot of files (at least one per second) so im wondering if either all the memory reserved for loading files is being given back to the system, or that the memory is becoming too fragmented because of all the memblocks being created/destroyed. I cant use the `load bitmap` function because this loads to a screen and i need it in workable memory, plus i want the .bmp header info available to read.

So basically:

Is there a memory leak/problem with the dll any1 else has found?
Would it be better to leave the memory block creation/destruction to the user manually rather than the dll doing it automatically, since im loading identical bitmaps each time i could reserve 1 memblock each time then just pass that pointer to the dll, something like below, or is there a better way of loading a bitmap without sending it to a screen first. DB really needs a BLOAD command like amos, so just BLOAD file$,ptr after 1st checking file size and reserving enough memory at `ptr`.

It's you

Use the DELETE QUEUED ITEM to return memory to windows when you've loaded the data into a memblock and finished with it.

Still, over an hour huh? Not bad

If you don't need asynchronous loading, use something like the following function (typed directly in - untested):

Hehe ty, i cant believe you can load a file to a memblock like that, i couldent see it in the db help >.< I was releasing the memory each time though using your loader, i virtually copied your example code and just changed the filenames.