search for: ast_taskprocessor_execute

Displaying 5 results from an estimated 5 matches for "ast_taskprocessor_execute".

2016 Jan 18
2
Segmentation Fault Asterisk 13.7.0-rc2 (libmysqlclient?)
...3 param = {start_prio = 0, start_mod = 0x7f1dccbe7500 <distributor_mod>, idx_after_start = 1, silent = 0} handled = 0 rdata = 0x7f1d4400e1e8 is_request = <optimized out> is_ack = 0 endpoint = <optimized out> #14 0x00000000005d28a1 in ast_taskprocessor_execute (tps=0x215c848) at taskprocessor.c:784 local = {local_data = 0x7f1dbc000c10, data = 0x5e4d12 <ast_threadstorage_set_ptr+60>} t = 0x7f1d44000920 size = 34981960 __PRETTY_FUNCTION__ = "ast_taskprocessor_execute" #15 0x00000000005db252 in execute_tasks (...
2017 May 09
2
asterisk 13.15.0 stopping/crashing
hi, i have strange problem with asterisk 13.15.0+pjsip bundled/centos 7/systemd start script we are using chan_pjsip only for webrtc endpoints . switched from sipml5 to jssip with upgrade to 13.15.0(from 13.9.0) few days ago today i have problems with stopping/crashing asterisk /var/log/asterisk/messages dont show any clues [May 9 12:10:52] WARNING[25762] pjproject: tsx0x7fbb28024088
2023 Aug 09
1
[External] Encountered a crash, what is best way to tell if it has been fixed or now
...77bc71b3a in stateless_send_resolver_callback (status=<optimized out>, token=0x7f773c635950, addr=<optimized out>) at ../src/pjsip/sip_util.c:1377 #12 0x00007f77380c3398 in sip_resolve_invoke_user_callback (data=0x7f773c4563c8) at res_pjsip/pjsip_resolver.c:206 #13 0x000055e7c0a6f0e3 in ast_taskprocessor_execute (tps=tps at entry=0x7f775416ebc0) at taskprocessor.c:1302 #14 0x000055e7c0a76d28 in execute_tasks (data=0x7f775416ebc0) at threadpool.c:1352 #15 0x000055e7c0a6f0e3 in ast_taskprocessor_execute (tps=0x55e7c2697720) at taskprocessor.c:1302 #16 0x000055e7c0a7760c in threadpool_execute (pool=0x55e7c269...
2017 Jun 18
2
asterisk 13.16. - sigseg during negotiation
...:704 #14 0x00007fba44b42b1e in pjsip_endpt_process_rx_data (endpt=0x36cc2a8, rdata=0x7fba3c0b00a8, p=0x7fba05c8d0a0, p_handled=0x7fb9f5901b7c) at ../src/pjsip/sip_endpoint.c:887 #15 0x00007fba05a72c59 in distribute (data=0x7fba3c0b00a8) at res_pjsip/pjsip_distributor.c:770 #16 0x00000000005ed6d1 in ast_taskprocessor_execute (tps=0x7fba3c0400a0) at taskprocessor.c:965 #17 0x00000000005f7056 in execute_tasks (data=0x7fba3c0400a0) at threadpool.c:1322 #18 0x00000000005ed6d1 in ast_taskprocessor_execute (tps=0x36bfab0) at taskprocessor.c:965 #19 0x00000000005f53a1 in threadpool_execute (pool=0x36c0040) at threadpool.c:351...
2023 Aug 09
2
Encountered a crash, what is best way to tell if it has been fixed or now
On Wed, Aug 9, 2023 at 3:20 PM Dan Cropp <dcropp at amtelco.com> wrote: > I have a customer who just encountered a crash while running Asterisk > 18.17.1 version. > > > > I’m trying to adapt to the changes so not sure where best to look or how > to possibly report this. > > > > I started by going through >