[BUG]: cudax uninitialized_buffer::get_resource
returns a resource_ref
that can dangle
#2430
Closed
1 task done
Labels
bug
Something isn't working right.
Is this a duplicate?
Type of Bug
Runtime Error
Component
libcu++
Describe the bug
cudax
uninitialized_buffer::get_resource
returns aresource_ref
that refers (in a non-owning way) to the memory resource owned by the buffer. if the returnedresource_ref
is then used to construct anotheruninitialized_buffer
, the new buffer will be left with a dangling reference once the first is destroyed.for instance, the following test fails (
test_device_memory_resource::count
is the number oftest_device_memory_resource
objects alive):How to Reproduce
see above
Expected behavior
i should be able to call
buffer.get_resource()
and construct a new buffer with the result that does not dangle whenbuffer
is destroyed.Reproduction link
No response
Operating System
No response
nvidia-smi output
No response
NVCC version
No response
The text was updated successfully, but these errors were encountered: