ESP32 Crashes when inputs like Sliders and Rollers have logic

[FudgeBot47]

Describe the bug
Sliders and Rollers work fine when they're purely graphical. but when logic is applied to them, after interacting with them 1-3 times, my ESP32 will either reboot with a Serial report or LVGL graphics and Flow logic will just stop functioning normally, with text disappearing and widgets being stuck.

Here are some reports from the Serial monitor:

ESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0x8 (TG1WDT_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT) Saved PC:0x40376a85 SPIWP:0xee mode:DIO, clock div:1 load:0x3fce2820,len:0x118c load:0x403c8700,len:0x4 load:0x403c8704,len:0xc20 load:0x403cb700,len:0x30e0 entry 0x403c88b8 ESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0x8 (TG1WDT_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT) Saved PC:0x40376a85 SPIWP:0xee mode:DIO, clock div:1 load:0x3fce2820,len:0x118c load:0x403c8700,len:0x4 load:0x403c8704,len:0xc20 load:0x403cb700,len:0x30e0 entry 0x403c88b8

`Guru Meditation Error: Core 0 panic'ed (InstrFetchProhibited). Exception was unhandled.

Core 0 register dump:
PC : 0xeaaebaba PS : 0x00060b30 A0 : 0x82061035 A1 : 0x3fcd2fb0
A2 : 0x3fcaf11c A3 : 0x00000005 A4 : 0x3fcaa728 A5 : 0x00000046
A6 : 0x3fcd3430 A7 : 0x3c1009a4 A8 : 0x82052188 A9 : 0x20202028
A10 : 0x00000000 A11 : 0x3fcaa728 A12 : 0x00000046 A13 : 0x00060723
A14 : 0x420559d4 A15 : 0x3fcaa650 SAR : 0x00000004 EXCCAUSE: 0x00000014
EXCVADDR: 0xeaaebab8 LBEG : 0x400556d5 LEND : 0x400556e5 LCOUNT : 0xfffffffa

Backtrace: 0x6aaebab7:0x3fcd2fb0 0x42061032:0x3fcd2fd0 0x4206066d:0x3fcd2ff0 0x420606be:0x3fcd3010 0x42060cbd:0x3fcd3030 0x4206b307:0x3fcd3060 0x4206ad0e:0x3fcd3080 0x420610a9:0x3fcd33a0 0x42073bed:0x3fcd33d0 0x420559e5:0x3fcd3400 0x42055a0d:0x3fcd3430 0x4205182e:0x3fcd3480 0x42051b5e:0x3fcd34d0 0x4201a7b5:0x3fcd35c0 0x4201a7d1:0x3fcd3600 0x4201a28f:0x3fcd3630 0x4203459a:0x3fcd3660 0x4201b90c:0x3fcd3680 0x42036a46:0x3fcd36d0 0x4201a36c:0x3fcd3700 0x4037cfba:0x3fcd3720`

My best guess is this has something to do with ESP32's limited memory (I'm using a ESP32-S3-Touch-AMOLED-1.91 specifically) But how might I optimize or troubleshoot my EEZ project to prevent this?

Screenshots
Here is some more specific context. I could produce these bugs by having a slider or roller with an assignable in the 'selected'.

here is a video of what the bugs look like:

20250630_112019.mp4

What I'm trying to do specifically, is control the PWM properties of an LED using two rollers, here is a screenshot of that setup, my best guess is these functions and logic are being called too many times too fast for the ESP32.

Desktop (please complete the following information):

• OS: Windows
• Version 10

LVGL version (if used)

• 8.x

[FudgeBot47]

I've made a further discovery: my function calls seem to be working correctly, the source of the error for some reason is when 'Selected 'in the 'SPECIFIC' properties of a Roller or Slider is set to an Assignable rather than a Literal, then it bugs out the ESP32.
The program works normally in the EEZ debugger.