Method zero_ref_callback

src/impl_core.cpp:622–636

This is weird. When a mem block is zonbiefied, its cpu memory allocation is already gone. This can cause issues when we want to later use it in destruction of memory block suballocated resources.

// When a mem block is zonbiefied, its cpu memory allocation is already gone.
// This can cause issues when we want to later use it in destruction of memory block suballocated resources.
void daxa_ImplMemoryBlock::zero_ref_callback(ImplHandle const * handle)
{
    auto const * self = r_cast<daxa_ImplMemoryBlock const*>(handle);
    std::unique_lock const lock{self->device->zombies_mtx};
    u64 const submit_timeline_value = self->device->global_submit_timeline.load(std::memory_order::relaxed);
    self->device->memory_block_zombies.emplace_front(
        submit_timeline_value,
        MemoryBlockZombie{
            .allocation = self->allocation,
        });
    self->device->dec_weak_refcnt(
        daxa_ImplDevice::zero_ref_callback,
        self->device->instance);
    delete self;
}

// --- End daxa_ImplMemoryBlock ---