Looking for insight into memory leaks

[bill-call]

I am getting a lot of memory leaks when I shut my test application normall (by closing the window). They come from many locations, but

DiligentEngine\DiligentCore\Graphics\GraphicsAccessories\interface\ResourceReleaseQueue.hpp(231) : {2188766} normal block at 0x00000250694F2380, 39 bytes long.

seems to dominate. The size suggests a texture not being freed. All of my resources are managed either through Diligent::RefCntAutoPtr<> or std::unique_ptr, so I am not sure why this is occurring. I have tried manually resetting the pointers, but that did not help. Keep in mind that this application is built as a new tutorial, so it usess the tutorial infrastructure.

I am not asking anyone to debug my app; just looking for some advice on where to focus my search.

[TheMostDiligent]

The size of the block is 39 bytes, so it is not a texture. CPU data does not go into the release queue, only the GPU resources.

There are no leaks in sample applications, so find what is different with your application.
If you are using global application pointer, it should be reset before exiting the app.