Allocate stat = 41

[Intel_C_Intel]

Steve,

I am facing an strange problem. I am trying to allocate a two dimensional pointer array (double precisioin) with size of (284544,151) and I am getting stat = 41. My computer has 3.5 GB RAM and system monitor shows only a total of 788 MB is in use out of which my program is using about 251 MB. Clearly, there is enough memory on the system. I am using MS visual studio .net 2005 with IVF 9.1.

I am actually moving to the new IVF/.NET setup from the old CVF/VStudio6 combo. The programs works fine with CVF6.6a and MS visual studio 6. I even tried runing both setups at the same time .NET/IVF and VS/CVF in debug mode starting with .NET/IVF. Once I got STAT=41, I let it stay there without terminating the program and ran CVF/VS and it runs fine which tells me that I have enough memory.

Is there any project setting I need to look at.

Thanks,
Ravi

[Steven_L_Intel1]

First, no matter how much RAM you have, the 32-bit Windows virtual memory limit is 2GB.

Nothing comes to mind immediately. Please submit an issue to Intel Premier Support and attach a ZIP of a test case project.

[Intel_C_Intel]

Here is an update, I had specified an stack size of 500MB for this project. When I reduce it to 200 MB, the code runs fine. Well, this gives me a workaround but CVF/VS6 worked with stack size of 500MB as well. I have no idea why stack size specified made a difference.

[Steven_L_Intel1]

Well, that's 300MB more available in your address space. Please do send a test case to Intel Premier Support - we'd like to see it.

[Intel_C_Intel]

I understand the extra 300MB in address space, but why it does not run with stack 500Mb while CVF/VS6 combination works.
The code that I am working on is proprietory so I can not send the project. I have been trying to duplicate this problem with a small test case but I doubt I will able to do that. Everything works just like it should in test cases.

[Wendy_Doerner__Intel]

Ravi,

The two compilers may be using the address space in different ways with the same code so as Steve mentions it would be hard to know exactly what is causing the increase need without code.