ATS 10.0.0 Crashes with SEGMENTATION FAULT #8959
Description
While i am trying to stream a video content through the ATS I sometimes get a crash relating to this. This might be some issue related to the configuration but the only configuration i am doing here that is
map https://domainofsite.com/ http://ip_of_origin:8080/ @plugin=header_rewrite.so @pparam=/var/test/rules1.conf
rules1.conf
cond %{READ_RESPONSE_HDR_HOOK}
set-status 200
set-header access-control-allow-origin https://domain.site.base
set-header access-control-allow-methods OPTIONS, GET, POST
set-header access-control-allow-credentials true
set-header access-control-allow-headers Authorization, Origin
(gdb) bt
#0 response_get (this=<optimized out>) at /home/nischal/trafficserver/proxy/hdrs/HTTP.h:1388
#1 HttpTransact::HandleCacheOpenReadHit (s=0x2b2559e43ee0) at HttpTransact.cc:2803
#2 0x000000000057a911 in HttpSM::call_transact_and_set_next_state (this=0x2b2559e43de0, f=<optimized out>) at HttpSM.cc:7534
#3 0x000000000058db41 in HttpSM::state_api_callout (this=0x2b2559e43de0, event=<optimized out>, data=<optimized out>) at HttpSM.cc:1620
#4 0x0000000000599f8b in HttpSM::set_next_state (this=0x2b2559e43de0) at HttpSM.cc:7576
#5 0x000000000057d6d5 in HttpSM::do_hostdb_lookup (this=this@entry=0x2b2559e43de0) at HttpSM.cc:4315
#6 0x000000000059a172 in HttpSM::set_next_state (this=0x2b2559e43de0) at HttpSM.cc:7877
#7 0x000000000058db41 in HttpSM::state_api_callout (this=0x2b2559e43de0, event=<optimized out>, data=<optimized out>) at HttpSM.cc:1620
#8 0x0000000000599f8b in HttpSM::set_next_state (this=0x2b2559e43de0) at HttpSM.cc:7576
#9 0x000000000058db41 in HttpSM::state_api_callout (this=0x2b2559e43de0, event=<optimized out>, data=<optimized out>) at HttpSM.cc:1620
#10 0x0000000000599f8b in HttpSM::set_next_state (this=0x2b2559e43de0) at HttpSM.cc:7576
#11 0x00000000005902b3 in HttpSM::state_cache_open_read (this=0x2b2559e43de0, event=1102, data=<optimized out>) at HttpSM.cc:2672
#12 0x0000000000591988 in HttpSM::main_handler (this=0x2b2559e43de0, event=1102, data=0x2b2559e45cb0) at HttpSM.cc:2736
#13 0x00000000006135e3 in handleEvent (data=0x2b2559e45cb0, event=1102, this=0x2b2559e43de0) at /home/nischal/trafficserver/iocore/eventsystem/I_Continuation.h:219
#14 HttpCacheSM::state_cache_open_read (this=0x2b2559e45c48, event=<optimized out>, data=<optimized out>) at HttpCacheSM.cc:118
#15 0x00000000007746cf in handleEvent (data=0x2b2574056c40, event=1102, this=0x2b2559e45c48) at /home/nischal/trafficserver/iocore/eventsystem/I_Continuation.h:219
#16 CacheVC::callcont (this=this@entry=0x2b2574056c40, event=event@entry=1102) at P_CacheInternal.h:650
#17 0x000000000076f45f in CacheVC::openReadStartEarliest (this=0x2b2574056c40) at CacheRead.cc:996
#18 0x000000000074a54d in CacheVC::handleReadDone (this=0x2b2574056c40, event=<optimized out>, e=<optimized out>) at Cache.cc:2289
#19 0x000000000074df89 in AIOCallbackInternal::io_complete (this=0x2b2574056dd0, event=<optimized out>, data=<optimized out>) at /home/nischal/trafficserver/iocore/aio/P_AIO.h:122
#20 0x00000000008a195f in handleEvent (data=0x1c57440, event=1, this=<optimized out>) at I_Continuation.h:219
#21 EThread::process_event (this=0x2b254d6b1010, e=0x1c57440, calling_code=1) at UnixEThread.cc:153
#22 0x00000000008a1f06 in EThread::process_queue (this=this@entry=0x2b254d6b1010, NegativeQueue=NegativeQueue@entry=0x2b254e2f0330, ev_count=ev_count@entry=0x2b254e2f032c,
nq_count=nq_count@entry=0x2b254e2f0328) at UnixEThread.cc:188
#23 0x00000000008a291d in EThread::execute_regular (this=this@entry=0x2b254d6b1010) at UnixEThread.cc:244
#24 0x00000000008a3732 in EThread::execute (this=0x2b254d6b1010) at UnixEThread.cc:349
#25 0x00000000008a0e32 in spawn_thread_internal (a=0x1c52f40) at Thread.cc:79
#26 0x00002b2549f5fea5 in start_thread () from /lib64/libpthread.so.0
#27 0x00002b254ac96b0d in clone () from /lib64/libc.so.6
(gdb)
Can anybody point me towards any reason why this might occur ?