[
https://issues.apache.org/jira/browse/TS-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655669#comment-13655669
]
Leif Hedstrom commented on TS-1891:
-----------------------------------
I was going to reply to James, but I see the comment above. Yes, the
double-free checking has been there forever, I thought?
Also, and a bit off topic, I'm a little concerned about the coupling with
thread specific allocations and the reclaimable freelist. Why are these
combined into one feature? It really messed up things, when we want to move
towards proxy allocators to replace the global allocators. (There's at least
one or two other bugs related to this issue).
> Add double-free checking for reclaimable freelist
> -------------------------------------------------
>
> Key: TS-1891
> URL: https://issues.apache.org/jira/browse/TS-1891
> Project: Traffic Server
> Issue Type: New Feature
> Components: Core
> Reporter: Yunkai Zhang
> Attachments:
> 0001-Add-double-free-checking-for-reclaimable-freelist-V2.patch
>
>
> double-free checking is very useful for us to analyze memory issues.
> So, I introduce this feature to recalimable freelist.
> The double-free checking for reclaimable freelist is disable by default,
> users can enable it by setting the following option in records.config:
> {code}
> CONFIG proxy.config.allocator.check_double_free INT 1
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
