[jira] [Commented] (TS-640) Repeated INKInit() / INKTerminate() will leak lots of memory

["Yunkai Zhang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744819#comment-13744819 ] 

Yunkai Zhang commented on TS-640:
---------------------------------

In my testing, we didn't fix this bug. There are memory leak when call TsInit() without option in a loop:

{code}
int
main(int argc, char *argv[])
{ 
  while (true) {
    TSInit("/var/run/trafficserver", static_cast<TSInitOptionT>(0));
    TSTerminate();
    sleep(1);
  }
}
{code}

When I analyzing TS-2141 issue, I found that before applied this commit: ba95f9c6e8c49f69f018885f255db02f31d7335f , traffic_cop would *reconnect* to traffic_manager automatically by *socket_test_thread* thread. But this commit introduce *TS_MGMT_OPT_NO_SOCK_TESTS* option to disable it.

Maybe we should fix the root cause of memory leak, rather than disable *socket_test_thread* simply.

Let me dig more ...
                
> Repeated INKInit() / INKTerminate() will leak lots of memory
> ------------------------------------------------------------
>
>                 Key: TS-640
>                 URL: https://issues.apache.org/jira/browse/TS-640
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Management API
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 2.1.6
>
>
> If you do
> INKInit();
> INKTerminate()
> repeatedly, the process will leak memory something fiercely. 

--
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