ESP32 Crashing after 10 - 20 mins of running

[LiveRock]

My program crash after running 10 - 20 mins.
I have LCD touchscreen, 2 sensors, ESP-NOW and serial input/output.
I am running TaskScheduler with 2-3 Tasks and ESP-NOW callbacks for data sent and receive.
ESP-NOW is used to send data from many slaves to the Master.
It is the Master that crashed.

Here is the error:

Code: [Select all] [Expand/Collapse]

1. Task watchdog got triggered. The following tasks did not reset the watchdog in time: E (677151)
2. task_wdt: - IDLE0 (CPU 0) E (677151)
3. task_wdt: Tasks currently running: E (677151)
4. task_wdt: CPU 0: wifi E (677151)
5. task_wdt: CPU 1: loopTask E (677151)
6. task_wdt: Aborting. abort() was called at PC 0x40195cd4 on core 0

GeSHi © Codebox Plus Extension

I have sent the last 5 days trying to solve this with no avail.
I tried removing all my PSRAM variables back to normal RAM to increase speed for painting screen, putting the ESP-NOW sending on a separate core, etc.

Here is my program in general.
1.2 -3 tasks doing screen painting and sensor capture.
2.1 task sending data via ESP-NOW
3. ESP-NOW callbacks function when data received
4. Monitor serial input because I need to generate serial output when connected to a computer
5. Handle screen touches

Here is my loop:

Code: [Select all] [Expand/Collapse]

1. void loop() {
2.  
3.   vTaskDelay(100 / portTICK_PERIOD_MS);
4.   meterScreenHandleButtons();
5.   userScheduler.execute();
6.  
7.   // Serial Communications
8.   if(Serial.available() && (selectedOperation != SLAVE)) {
9.     processSerialCommand(Serial.readStringUntil('\r\n'));
10.   }
11.  
12. }

GeSHi © Codebox Plus Extension

Any pointers?

[alanesq]

I know it seems trivial, but are you sure the power to the esp32 is good?
I can't tell you how many hours I have wasted chasing strange problems like this only to discover it is just a power issue.