You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Ricky Chan (JIRA)" <ji...@apache.org> on 2011/05/20 10:41:48 UTC

[jira] [Updated] (TS-793) the freelist dump function are not showing the correct values

     [ https://issues.apache.org/jira/browse/TS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ricky Chan updated TS-793:
--------------------------

    Attachment: ink_queue.patch

This is for 2.0.1 (but the same issue appears in 2.1.7)

> the freelist dump function are not showing the correct values
> -------------------------------------------------------------
>
>                 Key: TS-793
>                 URL: https://issues.apache.org/jira/browse/TS-793
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Cleanup, Core
>    Affects Versions: 2.1.7, 2.0.1
>         Environment: Linux Debian 5.0 (2.6.26 Kernel) on AMD64.
>            Reporter: Ricky Chan
>            Priority: Trivial
>              Labels: Debug
>         Attachments: ink_queue.patch
>
>
> I'm tracking a memory leak in 2.0.1 (possibly exists in latest versions too) and I am relying on the freelist_dump from when a USR1 signal is sent to gather information to determine where a memory leak is happening (I lose 5G a day).
> I notice that it started showing negative numbers pretty quickly when one of the lists was using more than 2G, so I looked in the code and found fprintf was using %d, considering the storage for allocated, type_size,count are unsigned 32 bit integers, that explained the zero.
> I have patched my code to use unsigned and unsigned long long to avoid me losing information in these dumps.
> I checked at this is still the case in at least 2.1.7.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira