I am doing some profiling with the peripheral_uart sample. It works as expected when I send small pieces of data, but when I start running a lot through it I get a crash. The log indicates it's a heap corruption issue due to free being called twice on the same pointer? I've captured the log at the point of the crash, and there does appear to be a double "rx_buf_released" right before it happens. This is also the first point in the log where I see "rx_disabled", if that matters. Any advice on how to debug this further and move forward would be greatly appreciated.
[00:01:06.398,406] <dbg> peripheral_uart.uart_cb: rx_buf_request
[00:01:06.403,686] <dbg> peripheral_uart.uart_cb: rx_rdy
[00:01:06.403,717] <dbg> peripheral_uart.uart_cb: rx_buf_released
[00:01:06.403,717] <dbg> peripheral_uart.uart_cb: rx_buf_request
[00:01:06.407,165] <dbg> peripheral_uart.uart_cb: rx_rdy
[00:01:06.407,196] <dbg> peripheral_uart.uart_cb: rx_buf_released
[00:01:06.407,196] <dbg> peripheral_uart.uart_cb: rx_buf_request
[00:01:06.467,315] <dbg> peripheral_uart.uart_cb: rx_rdy
[00:01:06.467,834] <dbg> peripheral_uart.uart_cb: rx_rdy
[00:01:06.467,864] <dbg> peripheral_uart.uart_cb: rx_buf_released
[00:01:06.467,864] <dbg> peripheral_uart.uart_cb: rx_buf_released
[00:01:06.467,895] <dbg> peripheral_uart.uart_cb: rx_disabled
[00:01:06.467,926] <dbg> peripheral_uart.uart_cb: rx_buf_request
ASSERTION FAIL [chunk_used(h, c)] @ WEST_TOPDIR/zephyr/lib/os/heap.c:154
unexpected heap state (double-free?) for memory at 0x20008f6c
[00:01:06.959,167] <err> os: r0/a1: 0x00000004 r1/a2: 0x0000009a r2/a3: 0x20001758
[00:01:06.959,167] <err> os: r3/a4: 0xfffffffc r12/ip: 0x00000000 r14/lr: 0x00011073[0m
[00:01:06.959,197] <err> os: xpsr: 0x61000000
[00:01:06.959,197] <err> os: Faulting instruction address (r15/pc): 0x00027ad4
[00:01:06.959,197] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:01:06.959,228] <err> os: Current thread: 0x20001670 (unknown)
[00:01:07.537,811] <err> fatal_error: Resetting system
