Closed jakirkham closed 4 years ago
Argh. rmm::device_buffer uses device_memory_resource, and none of these seem to use rmmAlloc / rmmFree (rather, the other way around). Logging is implemented in rmm API, not in the memory resources.
Fixed with PR ( https://github.com/rapidsai/rmm/pull/297 ).
Describe the bug
When trying to use RMM's logging with
rmm_alloc
andrmm_free
in Python, this works fine. However when trying to use logging with RMM'sDeviceBuffer
in Python, logging appears not to capture any activity.Steps/Code to reproduce bug
Working case with the log using
rmm_alloc
andrmm_free
:Not working case with
DeviceBuffer
:Expected behavior
The allocation would still be tracked in the
DeviceBuffer
case.Environment details (please complete the following information):
rmm/print_env.sh
script to gather relevant environment detailsAdditional context
Came up when debugging issue ( https://github.com/rapidsai/ucx-py/issues/402 ).
Given
DeviceBuffer
is a thin wrapper aroundrmm::device_buffer
, am guessing this behavior begins there.cc @quasiben (who also saw this earlier)