ESP32-S3 beta0 release img stack overflows, when empty/no avm is flashed. about atomvm HOT 3 CLOSED

I wouldn't personally write it is due to the sdkconfig but rather that a workaround is to edit the sdkconfig.

I believe it is a deeper bug.

from atomvm.

I wouldn't personally write it is due to the sdkconfig but rather that a workaround is to edit the sdkconfig.

I believe it is a deeper bug.

agreed, updated issue.

from atomvm.

The crash happens inside esp-idf when calling esp_wifi_init(), and it can be reproduced enabling CONFIG_COMPILER_OPTIMIZATION_PERF=y.

It can be fixed setting as default pthread stack size (that is 3072) to the same used for main task, such as CONFIG_PTHREAD_TASK_STACK_SIZE_DEFAULT=3584, but even a smaller value works (such as 3200).

I think that esp_wifi_init() in most firmwares around is called from main, so likely it has been tested mostly with 3584 bytes stack.

I have 2 hypothesis about this bug:

• enabling optimizations slightly increases stack usage (such as gcc using different memory layout for stack frames, etc...)
• increased execution speed causes a different scheduling order, that makes the network initialization running on the pthread rather than the main task

I suggest changing stack size for any created scheduler thread in order to match the same stack size used to main, so behavior is consistent independently from which scheduler has been used.

Changing sdkconfig works too, but I don't think that increasing the default size for all threads is the right thing to do.

from atomvm.