- do not let `_remove_events_with_arg()` call to block on queue pertubation, otherwise it could deadlock
- in any case do not block on adding LWIP_TCP_POLL event to the queue, it does not make much sense anyway
due to poll events are repetitive
- `_get_async_event()` will discard LWIP_TCP_POLL events when q gets filled up
this will work in combination with throttling poll events when adding to the queue
Poor designed apps and multiple parallel connections could flood the queue with interleaved poll events
that can't be properly throttled or coalesced. So we can discard it in the eviction task after coalescing
It will work in this way:
- queue is up to 1/4 full - all events are entering the queue and serviced
- queue is from 1/4 and up to 3/4 full - new poll events are throttled on enqueue with linear probability
- queue is from 3/4 up to full top - all new poll events are ignored on enqueue and existing poll events
already in the queue are discarded on eviction with linear probability giving away priority for all other
events to be serviced. It is expected that on a new poll timer connection polls could reenter the queue
AsyncTCP
A fork of the AsyncTCP library by @me-no-dev.
Async TCP Library for ESP32 Arduino
This is a fully asynchronous TCP library, aimed at enabling trouble-free, multi-connection network environment for Espressif's ESP32 MCUs.
This library is the base for ESPAsyncWebServer
AsyncClient and AsyncServer
The base classes on which everything else is built. They expose all possible scenarios, but are really raw and require more skills to use.
Changes in this fork
-
Based on ESPHome fork
-
library.propertiesfor Arduino IDE users -
Add
CONFIG_ASYNC_TCP_MAX_ACK_TIME -
Add
CONFIG_ASYNC_TCP_PRIORITY -
Add
CONFIG_ASYNC_TCP_QUEUE_SIZE -
Add
setKeepAlive() -
Arduino 3 / ESP-IDF 5 compatibility
-
Better CI
-
Better example
-
Customizable macros
-
Fix for "Required to lock TCPIP core functionality". Ref: https://github.com/mathieucarbou/AsyncTCP/issues/27 and https://github.com/espressif/arduino-esp32/issues/10526
-
Fix for "ack timeout 4" client disconnects.
-
Fix from https://github.com/me-no-dev/AsyncTCP/pull/173 (partially applied)
-
IPv6
-
LIBRETINY support
-
LibreTuya
-
Reduce logging of non critical messages
-
Use IPADDR6_INIT() macro to set connecting IPv6 address
-
xTaskCreateUniversal function
Coordinates
mathieucarbou/AsyncTCP @ ^3.2.15
Important recommendations
Most of the crashes are caused by improper configuration of the library for the project. Here are some recommendations to avoid them.
I personally use the following configuration in my projects:
-D CONFIG_ASYNC_TCP_MAX_ACK_TIME=5000 // (keep default)
-D CONFIG_ASYNC_TCP_PRIORITY=10 // (keep default)
-D CONFIG_ASYNC_TCP_QUEUE_SIZE=64 // (keep default)
-D CONFIG_ASYNC_TCP_RUNNING_CORE=1 // force async_tcp task to be on same core as the app (default is core 0)
-D CONFIG_ASYNC_TCP_STACK_SIZE=4096 // reduce the stack size (default is 16K)