j7nhai commented on PR #10249: URL: https://github.com/apache/incubator-gluten/pull/10249#issuecomment-3187812234
> @j7nhai > > > Why is it still necessary to wait in this case? > > We used to have some issues causing memory leak even task has exited. For instance, [facebookincubator/velox#8198](https://github.com/facebookincubator/velox/issues/8198). > > But since we have already solved them I think the memory leak should not happen anymore, ideally. > > Are you using the newest Gluten build? @zhztheplayer Here is the usage leak log: ``` E20250814 17:32:41.672763 215 Memory.cpp:161] pools_.size() != 0 (1 vs 0). There are unexpected alive memory pools allocated by user on memory manager destruction: Memory Manager[capacity UNLIMITED alignment 64B usedBytes 0B number of pools 4 List of root pools: __sys_root__ usage 0B reserved 0B peak 0B __sys_shared_leaf__0 usage 0B reserved 0B peak 0B __sys_tracing__ usage 0B reserved 0B peak 0B __sys_caching__ usage 0B reserved 0B peak 0B __sys_spilling__ usage 0B reserved 0B peak 0B root usage 0B reserved 0B peak 8.00MB task.Gluten_Stage_2_TID_1959_VTID_12 usage 0B reserved 0B peak 8.00MB node.0 usage 0B reserved 0B peak 7.00MB op.0.0.0.TableScan usage 0B reserved 0B peak 6.53MB refcount 2 ``` it looks that the pool of TableScan does not release. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
