[
https://issues.apache.org/jira/browse/TS-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754371#comment-13754371
]
James Peach commented on TS-2164:
---------------------------------
Yeh I hit this when I was jiggling startup order for SSH key loading. Let's
look at this for 4.2.0.
> Race condition between NetProcessor and api_init()
> --------------------------------------------------
>
> Key: TS-2164
> URL: https://issues.apache.org/jira/browse/TS-2164
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, HTTP
> Reporter: Tomasz Kuzemko
>
> In proxy/Main.cc starting of NetProcessor before calling api_init() can lead
> to a segfault when an early connection is served because of accessing
> http_global_hooks in HttpClientSession::new_connection():
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffe5019700 (LWP 21479)]
> 0x0000000000564add in HttpClientSession::new_connection (this=0x15073c0,
> new_vc=0x152df20, backdoor=false) at HttpClientSession.cc:228
> 228 hooks_set = http_global_hooks->hooks_set;
--
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