how to deal with trigger interupted watchdog

[浮生半日闲12138]

I use ESP-IDF to develop my own programs, so that SPIRAM and MBedtls can be used, and MBedTls uses Spiram. My program will have the problem of ranging from the interrupt-seeking dogs. Official documentation, I guess it should be spiram when sending MBedtls. When TLS_WRITE appears, it may be too late to interrupt the dog to time overtime. I made an attempt to let the tls_write not so frequently called, but the program will still take timeout. Do you have a similar usage, do you have any problems, or do you have similar problems? Thank you for providing some investigations.

重启后log:
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x8 (TG1WDT_SYS_RST),boot:0xb (SPI_FAST_FLASH_BOOT)
Saved PC:0x403829f3
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3810,len:0x164c
load:0x403c9700,len:0xbe0
load:0x403cc700,len:0x2ee8
entry 0x403c9900
....
system_main: 1 times start,lasted reset reson: 5(ESP_RST_INT_WDT)

[浮生半日闲12138]

I found the reason because I used the error parameter when I used mbedtls_net_send, using the space of uninited space, and the size is large, which would cause the interrupt timer timeout timeout timeout