[FEA] Leak Tracking for java Table instances
Open
feature request
Java
Spark
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.1k
- Avg merge
- 3d 6m
- Merged PRs (30d)
- 278
Description
**Is your feature request related to a problem? Please describe.**
This is very similar to https://github.com/rapidsai/cudf/issues/8227 except this is for instances of Table. Table is not nearly as important as Scalar because it does not directly reference GPU memory. But it would still be very nice to not leak them as they can cause off heap memory to grow.
**Describe the solution you'd like**
The same leak tracking and debugging done for ColumnVector should be applied to Table. Except Table does not do reference counting so it should be much simpler.
Contributor guide
Assessment
This issue has not been assessed yet.