You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On ESP32 and ESP32-S3 I am seeing various exceptions and crashes related to the native modules.
It can be exceptions like TypeError: 'slice' object isn't callable. Or array object is not callable. Or tuple is not callable. Or sometimes the entire interpreter crashes.
I am seeing this both with emltrees, emliir and emlfft. At first, I thought this was due to something the C code did wrong. But I reduced several C examples down to a minimum, and would still hit the issue. Even one example with a plain function (no allocated objects) - and that function itself seems to dissapear. And the behavior is influenced by unrelated things in MicroPython - doing other things that allocate/collect is needed to trigger the issue.
The same code also runs fine on x64 or STM32, or RP2040 - so it seems ESP32 port specific.
The text was updated successfully, but these errors were encountered:
On ESP32 and ESP32-S3 I am seeing various exceptions and crashes related to the native modules.
It can be exceptions like
TypeError: 'slice' object isn't callable
. Orarray object is not callable
. Ortuple is not callable
. Or sometimes the entire interpreter crashes.I am seeing this both with
emltrees
,emliir
andemlfft
. At first, I thought this was due to something the C code did wrong. But I reduced several C examples down to a minimum, and would still hit the issue. Even one example with a plain function (no allocated objects) - and that function itself seems to dissapear. And the behavior is influenced by unrelated things in MicroPython - doing other things that allocate/collect is needed to trigger the issue.The same code also runs fine on x64 or STM32, or RP2040 - so it seems ESP32 port specific.
The text was updated successfully, but these errors were encountered: