Re: Memory corruption of DLL class object

Thank you. That was the correct diagnostic. Now the release config works:
MyMFCApp.exe /MD
renderer.dll /MD
nvImage.dll /MD

But for Debug:
MyMFCApp.exe /MDd
renderer.dll /MDd
nvImaged.dll /MDd (notice the 'd' for debug, Nvidia's convention)

I encounter loss of internal data in nvImage.dll depending whether in
MyMFCApp.exe or renderer.dll it is accessed.

Some nvImage.dll functions:

void nv::Image::create(int w, int h)
{
this->stdVectorOfFloatPtrs.push_back( new float[w*h*4] );
this->width = w;
this->height = h;
}

float* nv::Image::getLevel( int i)
{
return this->stdVectorOfFloatPtrs[i];
}

In myMFCApp.exe:

//created on the heap in myMFCApp.exe
nv::Image* pImage = new nv::Image();

//create a buffer on the heap in nvImage.dll
pImage->create(256,256);

//Still in MyMFCApp.exe. Check data exists. Yes it does.
float* internalData = pImage->getLevel(0);

//Pass the pointer and program control to renderer.dll
myRenderer->modifyImage( pImage );

void renderer::modifyImage( nv::Image* pImage)
{
//If examine pImage->stdVectorOfFloatPtr here it has size 1

//As soon as I step into getLevel(), which is in nvImage.dll
//pImage's stdVectorOfFloatPtr has size 0 rather than 1
//width and height however are still 256
//Thus access violation is triggered here
float* internalData = pImage->getLevel(0);

//subsequent code to modify internalData
}

How is the data lost? Are there some different heap spaces issue for dlls?