ESP32 Forum

I've encountered that when using official MDF_LOGs in a created Task I need an additional +1500 bytes of memory. If I don't do that, then stack overflow happens... and it reboots the esp32.
If I set the MDF_LOGs to low level so that they don't get activated, then there is no issue, but when the level is higher, then stack overflow happens...

Shouldn't the MDF_LOGs do a simple print a formatted string?, how is that it needs so much memory?

I hope you can give a little bit of clearance.

Thanks,

I have similar issue too. I have try to use the console command log -t none to disable the output, but the chip restart after a while. using log -t <tag> seem also cannot filter any message. Do anyone have guideline/example for using the MDF_LOGs? Thanks.