[
https://issues.apache.org/jira/browse/TS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156364#comment-15156364
]
ASF GitHub Bot commented on TS-4212:
------------------------------------
Github user PSUdaemon commented on the pull request:
https://github.com/apache/trafficserver/pull/489#issuecomment-186967151
@jpeach,
I can't speak to the relative ugliness of the code. It's fairly C-ish like
the rest of our memory related code.
I don't think the current implementation of ats_malloc tracks any size.
I thought malloc had no specific guarantees on alignment, but usually
provides 8 byte alignment? Perhaps @bryancall can move the extra byes to the
end?
Can you use `malloc_usable_size` on a specific category of memory
allocation? Being able to pass in the counter here allows you to strictly
control which allocations are being tracked.
> Add option to track memory allocation with OpenSSL
> --------------------------------------------------
>
> Key: TS-4212
> URL: https://issues.apache.org/jira/browse/TS-4212
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, SSL
> Reporter: Bryan Call
> Fix For: 6.2.0
>
>
> For example:
> {code}
> [bcall@l1 ~]$ sudo traffic_line -s proxy.config.res_track_memory -v 2
> [bcall@l1 ~]$ sudo kill -sigusr1 $(pidof traffic_server); tail traffic.out
> Total Allocated | Total Freed | Currently Allocated | Type
> ---------------------|----------------------|----------------------|----------------------
> 18437960662 | 17181254510 | 1256706152 | SSL
> Allocated Memory
> ---------------------|----------------------|----------------------|----------------------
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
