Skip to content

[Bug]: Meshtastic node crashes after 12h when connected to a TCP client #7706

Description

@bergie

Category

WiFi

Hardware

Heltec V3

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

  • Meshtastic UI aka MUI colorTFT
  • InkHUD ePaper
  • OLED slide UI on any display

Firmware Version

2.7.4 (and 2.6.11)

Description

I'm experiencing a crashing issue with Meshtastic on a Heltec V3.2. This occurs with both firmware 2.6.x and 2.7.4. The node runs happily, but once network client (built with the JS library) connects and starts communicating, the node will reboot (crash?) after 12h (15h with 2.7.x).

So far tested:

  • Problem is the same with both 2.6 and 2.7 firmware
  • Using IP instead of MDNS address has no effect
  • DHCP lease times (or configuring static IP) has no effect
  • Same happens both using HTTP or plain TCP to talk to the node
  • Whether text messages are sent and received doesn't seem to have an effect
  • Verified to happen with two different Heltec devices on two different boats (so, different WiFi setup, different power setup, etc)

The client listens for text messages, and sends occasional (every few minutes) SetFixedPosition or EnvironmentTelemetry.

Relevant log output

Before the crash we start seeing these:


DEBUG | 06:48:04 65871 [RadioIf] Packet TX: 600ms
DEBUG | 06:48:04 65871 [RadioIf] 1 packets remain in the TX queue
INFO  | 06:48:04 65871 Tell client we have new packets 3019
DEBUG | 06:48:04 65872 [ServerAPI] FromRadio=STATE_SEND_PACKETS
DEBUG | 06:48:04 65872 [ServerAPI] phone downloaded packet (id=0xd2a0de2f fr=0xa0cb1d94 to=0xffffffff, WantAck=0, HopLim=3 Ch=0x0 Portnum=67 rxtime=175575
8883 priority=10)
[65872766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"
[65873766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"
[65874766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"
[65875766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"
[65876766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"
[65877766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"
[65878766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"
[65879766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"
[65880766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"
[65881766][E][WiFiClient.cpp:429] write(): fail on fd 52, errno: 11, "No more processes"


Then the crash itself:


INFO  | 06:48:16 65883 [Router] Received DeviceTelemetry from=0xdb294c58, id=0xbf1bab8d, portnum=67, payloadlen=22
DEBUG | 06:48:16 65883 [Router] Module 'DeviceTelemetry' considered
DEBUG | 06:48:16 65883 [Router] Module 'EnvironmentTelemetry' wantsPacket=1
INFO  | 06:48:16 65883 [Router] Received EnvironmentTelemetry from=0xdb294c58, id=0xbf1bab8d, portnum=67, payloadlen=22
INFO  | 06:48:16 65883 [Router] (Received from SYA): barometric_pressure=1012.363464, current=0.000000, gas_resistance=0.000000, relative_humidity=71.5810
55, temperature=30.430000
INFO  | 06:48:16 65883 [Router] (Received from SYA): voltage=0.000000, IAQ=0, distance=0.000000, lux=0.000000, white_lux=0.000000
INFO  | 06:48:16 65883 [Router] (Received from SYA): wind speed=0.000000m/s, direction=0 degrees, weight=0.000000kg
INFO  | 06:48:16 65883 [Router] (Received from SYA): radiation=0.000000##R/h
DEBUG | 06:48:16 65883 [Router] Module 'EnvironmentTelemetry' considered
DEBUG | 06:48:16 65883 [Router] Module 'PowerTelemetry' wantsPacket=1
INFO  | 06:48:16 65883 [Router] Received PowerTelemetry from=0xdb294c58, id=0xbf1bab8d, portnum=67, payloadlen=22
DEBUG | 06:48:16 65883 [Router] Module 'PowerTelemetry' considered
DEBUG | 06:48:16 65883 [Router] Module 'routing' wantsPacket=1
INFO  | 06:48:16 65883 [Router] Received routing from=0xdb294c58, id=0xbf1bab8d, portnum=67, payloadlen=22
DEBUG | 06:48:16 65884 [Router] Routing sniffing (id=0xbf1bab8d fr=0xdb294c58 to=0xffffffff, WantAck=0, HopLim=2 Ch=0x0 Portnum=67 rxtime=1755758895 rxSNR
=6.25 rxRSSI=-44 hopStart=3 relay=0x
INFO  | 06:48:16 65884 [Router] Rebroadcast received floodmsg

assert failed: T* MemoryDynamic<T>::alloc(TickType_t) [with T = _meshtastic_MeshPacket; TickType_t = unsigned int] MemoryPool.h:95 (p)


Backtrace: 0x40377b42:0x3fceba50 0x40380fb9:0x3fceba70 0x40387719:0x3fceba90 0x4205d475:0x3fcebbc0 0x420048d3:0x3fcebbe0 0x42067a1e:0x3fcebc00 0x42069fc3:0x3fcebc90 0x4206a03d:0x3fcebcb0 0x42066c80:0x3fcebcd0 0x42054126:0x3fcebd00 0x420519aa:0x3fcebd20 0x420674a5:0x3fcebdc0 0x4206780a:0x3fcebe20 0x4206be02:0x3fcebe40 0x420826ee:0x3fcebe60 0x4206ca05:0x3fcebe80 0x42019fd1:0x3fcebed0




ELF file SHA256: 9c34cf2a6378fbe8

Rebooting...
^@?ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
st:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x42151a92
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x4bc
load:0x403c9700,len:0xbd8
load:0x403cc700,len:0x2a0c
entry 0x403c98d0
INFO  | ??:??:?? 0 

//\ E S H T /\ S T / C

INFO  | ??:??:?? 0 Booted, wake cause 0 (boot count 1), reset_reason=reset
DEBUG | ??:??:?? 0 Filesystem files (28672/1572864 Bytes):
DEBUG | ??:??:?? 0  /prefs/channels.proto (57 Bytes)
DEBUG | ??:??:?? 0  /prefs/config.proto (262 Bytes)
DEBUG | ??:??:?? 0  /prefs/device.proto (132 Bytes)
DEBUG | ??:??:?? 0  /prefs/module.proto (100 Bytes)
DEBUG | ??:??:?? 0  /prefs/nodes.proto (1188 Bytes)
DEBUG | ??:??:?? 0  /static/.gitkeep (0 Bytes)
[   552][I][esp32-hal-i2c.c:75] i2cInit(): Initialising I2C Master: sda=41 scl=42 freq=100000
[   565][I][esp32-hal-i2c.c:75] i2cInit(): Initialising I2C Master: sda=17 scl=18 freq=100000
DEBUG | ??:??:?? 0 Power::lipoInit lipo sensor is not ready yet
DEBUG | ??:??:?? 0 Use analog input 1 for battery level
...
`

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions