🚀 go-pugleaf

nagoyadam@gmail.com wrote:

>The error message I receive is "Not enough storage is available to
>process this command" I have 3GB RAM on my machine,

RAM isn't the issue.

> and the DLL requires around 600MB

That could well be the issue.
Programs are only alotted 2 GB of "space" in which to run.
Your program loads at the 4 MB mark.
Above that is your code, data, uninitialized data.
Above that, DLLs are loaded in a free-for-all. wherever they can fit.
First come, first served.
Then too, each thread that spawns after startup takes another MB for
it's stack.
Plus any allocated/fragmented data
And the memory manager takes a hunk of what's left over so it doesn't
need to keep asking the OS for memory.
By loading your DLL last, it has to make do with whatever is left.
Apparently you don't have a contiguous 600MB remaining.

Either that, or your DLL has been "based" so it can only go in one
position in memory, and some of that area is in use.

By letting the startup code manage the loading of your DLL, it can
rework the jigsaw puzzle entil everything fits.
Then the runtime allocations for thread stack and variables can fit
into the nooks and crannies left over.

>The DLL has a large matrix used internally and not exported can the
>linker know about it?

It knows how big the DLL is (well, maybe not the linker, but at least
the startup code it generates).

You might consider allocating the matrix at runtime if it isn't
preinitialized with data.