AsyncWebServer giving wdt reset
The following recommandations, as you are providing not enough relevant info


Install ESP-exeption decoder and analyse your backtrace - post it here so we see what indetail caused the wdt
Async webserver tends to cause this behavior if a response tends to take to long a well placed yield() sometimes helps to prevent that behavior - to anaylse you need ESP-exeption decoder
as loop() is running on core1 some/no process (idle) on core0 caused the behavior. You cann look up task assignment to cores be done manually to distribute the tasks (or send a yield() timed to core0 to reset the wdt
placing timeouts in combination with sleep/deep sleep (although you dont seem to use them) are also causes for wdt resets
a hackey trick is to set CONFIG_ASYNC_TCP_USE_WDT 0 but is ok for testing


If you look into async_tcp the possible culprit you see one line
xTaskCreateUniversal(_async_service_task, "async_tcp", 8192 * 2, NULL, 3, &amp;_async_service_task_handle, CONFIG_ASYNC_TCP_RUNNING_CORE);
   Here an example how I use it to prevent wdt resetsPlace in setup()

disableCore0WDT();
disableCore1WDT();
disableLoopWDT(); // You forgot this one !


and because of this routine in the async_tcp lib

static void _async_service_task(void *pvParameters){
    lwip_event_packet_t * packet = NULL;
   for (;;) {
    if(_get_async_event(&amp;packet)){
#if CONFIG_ASYNC_TCP_USE_WDT
        if(esp_task_wdt_add(NULL) != ESP_OK){
            log_e("Failed to add async task to WDT");
        }           
 #endif
        _handle_async_event(packet);
 #if CONFIG_ASYNC_TCP_USE_WDT
        if(esp_task_wdt_delete(NULL) != ESP_OK){
            log_e("Failed to remove loop task from WDT");
        }
#endif
    }
 }
  vTaskDelete(NULL);
   _async_service_task_handle = NULL;
}


I set the CONFIG_ASYNC_TCP_USE_WDT 0 and it works so far.