Error when running

"Is there anyone who can help? I am learning about WebServer and trying this link:

Then why does an error like this appear in the Serial Monitor window:

What does 'assert failed: tcp_alloc.....' mean?"

Sorry I cannot read your screen shot. Please capture it and post it as text.

Maybe you click the screenshoot.

Ok this are the message that I copy from Serial Monitor

Rebooting...
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:4916
load:0x40078000,len:16436
load:0x40080400,len:4
ho 8 tail 4 room 4
load:0x40080404,len:3524
entry 0x400805b8

Connecting to WiFi ...192.168.1.8
LittleFS mounted successfully

assert failed: tcp_alloc /IDF/components/lwip/lwip/src/core/tcp.c:1851 (Required to lock TCPIP core functionality!)

The last line above is written as follows:
assert failed: tcp_alloc /IDF/components/lwip/lwip/src/core/tcp.c:1851 (Required to lock TCPIP core functionality!)

My questions are:

  1. What does the message 'assert failed: tcp_alloc/IDF/components/ ....' mean?
  2. Why is it that when I access the address 192.168.1.8 through the browser, that address is not found?

Seems to be a known issue. I've not looked at the top search result.

1 Like

Maybe you follow the forum rules.

3 Likes

Replace ESPAsyncWebServer with ESP Async WebServer and AsyncTCP with Async TCP

1 Like

Replace ESPAsyncWebServer with ESP Async WebServer and AsyncTCP with Async TCP

This solved my problem but I didn't understand what it meant the first few times I saw it so I thought I would elaborate. I get the impression that the problem is old unsupported libraries are now broken and this comment is to switch from the older libraries to the new ones which have the exact same names but with added spaces in the names:

"ESPAsyncWebServer" change to library "ESP Async WebServer"
"AsyncTCP" change to library "Async TCP"

Did that and suddenly my code was compiling again with no changes!

Thanks for the correction frank1212!