Describe the bug
When running benchmarks with reduced off-heap memory allocated, I see these warnings. I am not sure if this is something we can fix, or is just the result of a drop happening after a panic, but I'd like to understand what is going on.
comet-benchmark-derived-from-tpch-08872799821543de-exec-6 spark-kubernetes-executor 25/09/25 18:45:19 WARN /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/jni-0.21.1/src/wrapper/objects/global_ref.rs: Dropping a GlobalRef in a detached thread. Fix your code if this message appears frequently (see the GlobalRef docs).
Steps to reproduce
No response
Expected behavior
No response
Additional context
No response
Describe the bug
When running benchmarks with reduced off-heap memory allocated, I see these warnings. I am not sure if this is something we can fix, or is just the result of a drop happening after a panic, but I'd like to understand what is going on.
Steps to reproduce
No response
Expected behavior
No response
Additional context
No response