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

Yunkai Zhang commented on TS-1735:
----------------------------------

It seems that reclaimable_freelist_init() was broken by ink_assert().

There are two ink_assert() within it:
{code}
void
reclaimable_freelist_init(InkFreeList **fl, const char *name,
                          uint32_t type_size, uint32_t chunk_size,
                          uint32_t alignment)
{
  /* quick test for power of 2 */
  ink_assert(!(alignment & (alignment - 1)));   //#1
  
  ...

  ink_assert(f->thread_cache_idx < MAX_NUM_FREELIST); //#2
}
{code}

I guess the #2 ink_assert() was triggered. Can you compile TS with 
--enable-debug options so that we can get more information  from backtrace? Or 
you can enlarge MAX_NUM_FREELIST's value in lib/ts/ink_queue_ext.cc and try 
again.
                
> reclaimable freelist causes core in osx
> ---------------------------------------
>
>                 Key: TS-1735
>                 URL: https://issues.apache.org/jira/browse/TS-1735
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>            Reporter: Bryan Call
>             Fix For: 3.3.1
>
>
> Global variable dependency and ininitialtion order can cause reclaimable 
> freelist to core.  Reclaimable freelist depends on a global mutex attribute.
> (gdb) bt
> #0  0x00007fff8fa17d46 in __kill ()
> #1  0x00007fff84824df0 in abort ()
> #2  0x00000001009ce697 in reclaimable_freelist_init (fl=<value temporarily 
> unavailable, due to optimizations>, name=<value temporarily unavailable, due 
> to optimizations>, type_size=<value temporarily unavailable, due to 
> optimizations>, chunk_size=<value temporarily unavailable, due to 
> optimizations>, alignment=<value temporarily unavailable, due to 
> optimizations>) at ink_mutex.h:80
> #3  0x00007fff5fc13378 in 
> __dyld__ZN16ImageLoaderMachO18doModInitFunctionsERKN11ImageLoader11LinkContextE
>  ()
> #4  0x00007fff5fc13762 in 
> __dyld__ZN16ImageLoaderMachO16doInitializationERKN11ImageLoader11LinkContextE 
> ()
> #5  0x00007fff5fc1006e in 
> __dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEjRNS_21InitializerTimingListE
>  ()
> #6  0x00007fff5fc0ffc4 in 
> __dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEjRNS_21InitializerTimingListE
>  ()
> #7  0x00007fff5fc0feba in 
> __dyld__ZN11ImageLoader15runInitializersERKNS_11LinkContextERNS_21InitializerTimingListE
>  ()
> #8  0x00007fff5fc01fc0 in __dyld__ZN4dyld24initializeMainExecutableEv ()
> #9  0x00007fff5fc05b04 in 
> __dyld__ZN4dyld5_mainEPK12macho_headermiPPKcS5_S5_Pm ()
> #10 0x00007fff5fc01397 in 
> __dyld__ZN13dyldbootstrap5startEPK12macho_headeriPPKclS2_Pm ()
> #11 0x00007fff5fc0105e in __dyld__dyld_start ()

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

Reply via email to