Re: [PR] [VL] Increase the frequency of calling tryDestructSafe, and make one final attempt at the end [incubator-gluten]

["j7nhai (via GitHub)" <gi...@apache.org>]

j7nhai commented on PR #10249:
URL: https://github.com/apache/incubator-gluten/pull/10249#issuecomment-3182657826

   > @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?
   
   I use the release 1.4.0 and when tryDestructSafe fail, it shows that ` veloxMemoryManager_->numPools()` is 4, with the INFO log:
   
   ```
   Attempt to destruct VeloxMemoryManager failed because there are 4 outstanding memory pools.
   ```


-- 
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: commits-unsubscribe@gluten.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@gluten.apache.org
For additional commands, e-mail: commits-help@gluten.apache.org