VitalPBX Asterisk crashed unhandled exception PJLIB/No memory!

Jbelectronics · September 1, 2026, 12:23am

VitalPBX Asterisk crashed and restarted with below error in the logs, Any way to diagnose what caused this and prevent this from happening again ?

[2026-08-31 06:41:35] ERROR[1664] pjproject: except.c …!!!FATAL: unhandled exception PJLIB/No memory!
[2026-08-31 06:41:35] ERROR[1664] pjproject: ../src/pj/except.c …Assert failed: handler != NULL
[2026-08-31 06:42:28] Asterisk 20.20.1 built by root @ pbx on a x86_64 running Linux on 2026-07-29 23:22:55 UTC

miguel · September 1, 2026, 12:23am

What version of VitalPBX is this?

Where’s the server hosted?

Is it a brand new server?

Jbelectronics · September 1, 2026, 1:07am

Hi,

No its not a brand new server been same server since almost a year now.

Its hosted on Linode, 6 core, 16 GB Ram.

Vital PBX Version: 4.5.3-8

Asterisk Version: 20.20.1

miguel · September 1, 2026, 2:57am

Check the thread below about this:

github.com/asterisk/asterisk

[bug]: FATAL: unhandled exception PJLIB/No memory!

opened 09:22PM - 30 Apr 24 UTC

mikepultz

bug support-level-core feedback-required

### Severity Major ### Versions 21.2.0 ### Components/Modules pjproject ##…# Operating Environment Amazon Linux 2 (RHEL) ### Frequency of Occurrence One Time ### Issue Description One of our Asterisk instances crashed today when trying to allocate memory to a pj_pool: `[2024-04-30 11:11:04] ERROR[28315]: pjproject:<?>: except.c ..!!!FATAL: unhandled exception PJLIB/No memory!` This is the first time it's happened, and we have 6 identical instances total (load balanced) that have been running for about a month, and so far it's only happened the once. The system is not experiencing memory issues, and it doesn't appear to be a memory leak (no visible downward trend over time in on our Available memory graphs): ![image](https://github.com/asterisk/asterisk/assets/4993169/1c4613cb-c56d-4637-b83e-1aa8d1e9f5eb) The servers are not under a high load - there was only around 120 active calls when this happened. I've included a backtrace from the core dump. It's a production device, so I'm not able to run it under Valgrind, but I can probably provide some redacted config files if that's helpful.. ### Relevant log output ```shell #0 0x00001479505e6cd0 in __longjmp_chk () from /lib64/libc.so.6 #1 0x0000147952e2952e in pj_throw_exception_ (exception_id=1) at ../src/pj/except.c:53 #2 0x0000147952d96f90 in pool_callback (pool=<optimized out>, size=<optimized out>) at ../src/pjsip/sip_endpoint.c:143 #3 0x0000147952e2d9f5 in pj_pool_create_block (size=7598263421698388000, pool=0x14792c65baa0) at ../src/pj/pool.c:62 #4 pj_pool_allocate_find (pool=0x14792c65baa0, size=7598263421698387232) at ../src/pj/pool.c:148 #5 0x0000147952e2da52 in pj_pool_alloc (pool=<optimized out>, size=<optimized out>) at ../include/pj/pool_i.h:61 #6 0x0000147952e39b59 in pj_strdup (pool=pool@entry=0x14792c65baa0, dst=dst@entry=0x147902c0f7f8, src=0x1e58c48) at ../include/pj/string_i.h:42 #7 0x0000147952d9fab9 in pjsip_tpmgr_find_local_addr2 (tpmgr=0x1e3f5c8, pool=pool@entry=0x14792c65baa0, prm=prm@entry=0x147902c0f7d0) at ../src/pjsip/sip_transport.c:1770 #8 0x000014790b63ada5 in filter_on_tx_message (tdata=0x14792c65bb48) at res_pjsip/pjsip_message_filter.c:253 #9 0x0000147952d96f3c in endpt_on_tx_msg (endpt=<optimized out>, tdata=0x14792c65bb48) at ../src/pjsip/sip_endpoint.c:1125 #10 0x0000147952d9e9a4 in pjsip_transport_send (tr=0x14793d6f9838, tdata=tdata@entry=0x14792c65bb48, addr=addr@entry=0x1479441374f4, addr_len=28, token=token@entry=0x147944137408, cb=cb@entry=0x147952db02b0 <transport_callback>) at ../src/pjsip/sip_transport.c:944 #11 0x0000147952db0715 in tsx_send_msg (tsx=0x147944137408, tdata=0x14792c65bb48) at ../src/pjsip/sip_transaction.c:2351 #12 0x0000147952db296e in tsx_on_state_proceeding_uas (event=0x147902c0fa50, tsx=0x147944137408) at ../src/pjsip/sip_transaction.c:2948 #13 tsx_on_state_trying (tsx=0x147944137408, event=0x147902c0fa50) at ../src/pjsip/sip_transaction.c:2878 #14 0x0000147952db4707 in pjsip_tsx_send_msg (tsx=0x147944137408, tdata=tdata@entry=0x14792c65bb48) at ../src/pjsip/sip_transaction.c:1969 #15 0x000014790b62bf61 in ast_sip_send_stateful_response (rdata=rdata@entry=0x14793ed75598, tdata=0x14792c65bb48, sip_endpoint=sip_endpoint@entry=0x14792cf94368) at res_pjsip.c:2460 #16 0x000014790b63178f in send_options_response (rdata=0x14793ed75598, code=code@entry=200) at res_pjsip/pjsip_options.c:256 #17 0x000014790b63190f in options_on_rx_request (rdata=<optimized out>) at res_pjsip/pjsip_options.c:305 #18 0x0000147952d97ca1 in pjsip_endpt_process_rx_data (endpt=0x1bdb5a8, rdata=rdata@entry=0x14793ed75598, p=p@entry=0x14790b87a400 <param>, p_handled=p_handled@entry=0x147902c0fc1c) at ../src/pjsip/sip_endpoint.c:930 #19 0x000014790b6466ef in distribute (data=0x14793ed75598) at res_pjsip/pjsip_distributor.c:952 #20 0x00000000005a0bee in ast_taskprocessor_execute () #21 0x00000000005a732b in execute_tasks () #22 0x00000000005a0bee in ast_taskprocessor_execute () #23 0x00000000005a7c81 in worker_start () #24 0x00000000005af939 in dummy_start () #25 0x00001479524e944b in start_thread () from /lib64/libpthread.so.0 #26 0x00001479505d652f in clone () from /lib64/libc.so.6 ``` ### Asterisk Issue Guidelines - [X] Yes, I have read the Asterisk Issue Guidelines