[
https://issues.apache.org/jira/browse/ARROW-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486444#comment-17486444
]
David Li commented on ARROW-15550:
----------------------------------
We could also enable debug assertions in jemalloc:
[http://jemalloc.net/jemalloc.3.html] "When so configured, jemalloc
incorporates a wide variety of run-time assertions that catch application
errors such as double-free, write-after-free, etc."
There's also mimalloc's secure/debug modes:
[https://github.com/microsoft/mimalloc#secure-mode]
Though these could be used in addition to having a custom pool.
> [C++] Add an environment variable to debug memory
> -------------------------------------------------
>
> Key: ARROW-15550
> URL: https://issues.apache.org/jira/browse/ARROW-15550
> Project: Apache Arrow
> Issue Type: Wish
> Components: C++, Developer Tools
> Reporter: Antoine Pitrou
> Priority: Major
>
> It could be useful to allow enabling memory checks at runtime (e.g. check
> that memory was not written out of bounds when a MemoryPool deallocates a
> buffer). For example an environment variable setting
> {{ARROW_DEBUG_MEMORY_POOL=(warn|trap|abort)}}
> See https://github.com/apache/arrow/pull/12216 for inspiration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
