Two questions about MemoryAllocator override

[hzqst]

1. Seems there is no way to override the g_pRawAllocator from Archiver dll?

I am getting crash on RefCountedObject dtor now as RenderStateCacheImpl was created with DefaultRawAllocator from Archiver dll (ms crt malloc in this case) instead of mi_malloc override.

A potential fix would be adding virtual SetRawAlloctor(IMemoryAllocator *) = 0; as a new interface in Archiver Factory.

2. I was playing with StringDataBlobImpl :

char shaderName[256]{};
//snprintf...
auto ShaderName = Diligent::StringDataBlobImpl::Create(shaderName);

however I found no MemoryAllocator override for StringDataBlobImpl, I have to go with DataBlobImpl as a workaround:

char shaderName[256]{};
//snprintf...
auto ShaderName = Diligent::DataBlobImpl::Create(&DiligentRenderer()->GetDefaultAllocator(), strlen(shaderName), shaderName);\

[TheMostDiligent]

Note that user-provided memory allocator is not rigorously used everywhere