[
https://issues.apache.org/jira/browse/TS-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100678#comment-13100678
]
Igor Galić commented on TS-567:
-------------------------------
There's another flavour of free which I discovered when reviewing r1166608 -
namely: FREE
{noformat}
igalic@tynix ~/src/asf/trafficserver (svn)-[trunk:1166671] % ack -lw FREE
test/plugin/include_other/macro.h
test/plugin/check-url/check-url-0.c
test/plugin/check-http/check-http-0.c
test/plugin/check-mime/check-mime-0.c
example/include_other/macro.h
igalic@tynix ~/src/asf/trafficserver (svn)-[trunk:1166671] % ack -w FREE | wc -l
38
igalic@tynix ~/src/asf/trafficserver (svn)-[trunk:1166671] %
{noformat}
> Cleanup of memory allocation in libinktomi++
> --------------------------------------------
>
> Key: TS-567
> URL: https://issues.apache.org/jira/browse/TS-567
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Priority: Critical
> Fix For: 3.1.1
>
> Attachments: clear_memory.patch, malloc.txt
>
>
> There's a lot of ifdef's and debugging code paths around various allocation
> schemes in libinktomi++. We should clean this up, and simplify. It'd also be
> great to make it easy to enable various other allocators, e.g. jemalloc or
> tcmalloc, as part of the build system, causing ink_malloc / xmalloc and STL
> containers to use the new allocator. In particular for STL containers, it
> means we might need to have some allocator setup / initialization?
> Also, when should we use ink_malloc() vs xmalloc() ? It's quite
> inconsistently used right now I think. And, there are a few places using
> malloc() (etc.) directly, which we ought to fix.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
