Regularly Dropping off the Network / Crashlog

[art103]

Hi,
I am using OVMS in our Nissan Leaf.
Since I bought it last year, it regularly falls off the network and stops updating (re-plug OBD connector to reset).
I switched from the 'main' OTA release to the 'edge' version hoping it would help. It did slightly: I now sometimes get a week rather than a day of uptime; however it still fails.
The car is in a good WiFi reception area when parked. LTE is good at home, but patchy around town.
WiFi: -68dBm, LTE: -77dBm

Is there a way to get the crash log when the device is not on the network?

I have the IDF build environment setup if there are any suggestions.

I checked the WebUI this morning (still connected):

Last boot was 46838 second(s) ago
Time at boot: 2023-07-30 18:35:53 BST
  This is reset #4 since last power cycle
  Detected boot reason: EarlyCrash (12/12)
  Reset reason: Stack overflow (4)
  Crash counters: 4 total, 3 early

Last crash: abort() was called on core 1
  Stack overflow in task tiT
  Current task on core 0: IDLE0, 436 stack bytes free
  Current task on core 1: tiT, 0 stack bytes free
  Backtrace:
  0x4008ddd2 0x4008e06d 0x40117a46 0x40090c7c 0x40091d64 0x40091d1a 0x40122919
  Event: system.modem.gotip@netmanager 0 secs
  Version: 3.3.003-520-gd844398b/ota_1/edge (build idf v3.3.4-849-g6e214dc33 Jul 23 2023 00:08:15)

  Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600
Hardware:          OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600
Firmware:          3.3.003-520-gd844398b/ota_1/edge (build idf v3.3.4-849-g6e214dc33 Jul 23 2023 00:08:15)
Running partition: ota_1
Boot partition:    ota_1
Factory image:     3.3.003-464-gbe52e30e
OTA_O image:       3.3.003-519-g105e47cf
OTA_1 image:       3.3.003-520-gd844398b

Edit: Another stack overflow

Last boot was 4114 second(s) ago
Time at boot: 2023-08-01 16:17:00 BST
  This is reset #8 since last power cycle
  Detected boot reason: Crash (12/12)
  Reset reason: Stack overflow (4)
  Crash counters: 8 total, 0 early

Last crash: abort() was called on core 0
  Stack overflow in task OVMS Cellular
  Current task on core 0: OVMS Cellular, 0 stack bytes free
  Current task on core 1: OVMS Events, 3920 stack bytes free
  Backtrace:
  0x4008ddd2 0x4008e06d 0x40117a46 0x40090c3c 0x40091d64 0x40091d1a
  Event: ticker.1@ovms-server-v3 0 secs
  Version: 3.3.003-520-gd844398b/ota_1/edge (build idf v3.3.4-849-g6e214dc33 Jul 23 2023 00:08:15)

  Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600
Hardware:          OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600
Firmware:          3.3.003-520-gd844398b/ota_1/edge (build idf v3.3.4-849-g6e214dc33 Jul 23 2023 00:08:15)
Running partition: ota_1
Boot partition:    ota_1
Factory image:     3.3.003-464-gbe52e30e
OTA_O image:       3.3.003-519-g105e47cf
OTA_1 image:       3.3.003-520-gd844398b

[art103]

Some additional information:
The last event logged by my local MQTT sever is usually either system.modem.netstart or server.v3.connected.
I believe the bug is somewhere around the code that manages switching between WiFi and LTE, possibly triggered by an intermittent LTE connection.

Edit:
I suspect this is related to the location streaming option. I had it set to 10s, but this isn't what is implemented. Any time a metric changes, OVMS will transmit it regardless of vehicle power.
My guess is that if this happens during a network switch, it locks up, and during normal operation it is likely to cause a stack overflow.

I have created a patch: #927
So far, 48 hours and no crashlog / reset.