davisusanibar opened a new issue, #37177: URL: https://github.com/apache/arrow/issues/37177
### Describe the enhancement requested At the beginning, it is harder to interact with memory allocation. It is also necessary for some applications to maintain only one RootAllocator, just as [here](https://arrow.apache.org/docs/java/memory.html#development-guidelines:~:text=instead%20of%20RootAllocator.-,Create%20one%20RootAllocator%20at%20the%20start%20of%20the%20program,-.) is recommended. The singleton allocation will also be helpful in detecting memory leaks as the unreleased allocators can be cross validated. The Single Allocator must also be able to create enumerated and identified child allocators. Enhancement requested: 1. Create a Singleton Allocator 2. Incorporate Singleton Allocator for same functionalities that is tested using RootAllocator (main idea is try to identify or detecting allocator leaks on current testing scenarios or created another ones) 3. Validate/create SingletonAllocator thread-safe I would also like to thank @adamkennedy for these recommendations. ### Component(s) Documentation, Java -- 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]
