Also, the Release function returns what the new value of the ref-count is after the call. You can add some assertions in your release-on-lost-device code, checking that those values are zero -- if they're greater than zero, then you've leaked some references somewhere.
He was making a reference of his own to this:“lonewolf, what does the PIX say about his reference count?”the object's ref-count is over 9000!
“It’s over 9,000!!!!”
L. Spiro
No, that was an example by Hodgman. It isn't over 9000 at all. ;)
//This is called every frame
if(!FAILED(d3dDevice->GetBackBuffer(0,0,D3DBACKBUFFER_TYPE_MONO,&surfaceBackbuffer)))
{
DstRect.left=0;
DstRect.top=0;
DstRect.right=nWindowWidth;
DstRect.bottom=nWindowHeight;
if(FAILED(d3dDevice->StretchRect(surfaceApplication,NULL,surfaceBackbuffer,&DstRect,D3DTEXF_LINEAR )))
return 141;
// ADDED THIS TO THE CODE
if(surfaceBackbuffer)
{
surfaceBackbuffer->Release();
surfaceBackbuffer=NULL;
}
}Does StretchRect ever fail? If so, you're not releasing the surface reference.
the object's ref-count is over 9000!
“lonewolf, what does the PIX say about his reference count?”
“It’s over 9,000!!!!”
L. Spiro
I would rate this up just on comedic value, but I think that trivializes the ratings system.
