Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashes when leds length is 3 #4120

Closed
1 task done
Andro-Marian opened this issue Aug 27, 2024 · 12 comments
Closed
1 task done

Crashes when leds length is 3 #4120

Andro-Marian opened this issue Aug 27, 2024 · 12 comments
Labels
bug confirmed The bug is reproducable and confirmed fixed in source This issue is unsolved in the latest release but fixed in master

Comments

@Andro-Marian
Copy link

What happened?

WLed crashes when setting some effects like Fireworks 1D

To Reproduce Bug

  1. Set the Length of leds to 3
  2. Set the effect to Fireworks 1D

Expected Behavior

To work fine.

Install Method

Binary from WLED.me

What version of WLED?

0.14.4, 0.15.0-b4

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

abort() was called at PC 0x4008f49c on core 0

ELF file SHA256: 0000000000000000

Backtrace: 0x4008a7b8:0x3ffb7710 0x4008ab15:0x3ffb7730 0x4008f49c:0x3ffb7750 0x4008f9b4:0x3ffb7770 0x4008600d:0x3ffb7790 0x4008603e:0x3ffb77b0 0x4008645d:0x3ffb77d0 0x4000beaf:0x3ffb77f0 0x40084081:0x3ffb7810 0x4018a2b1:0x3ffb7830 0x401a1ce9:0x3ffb7850 0x4019cf91:0x3ffb7870 0x4014dc73:0x3ffb7890 0x4014dcdb:0x3ffb78b0 0x4008c55e:0x3ffb78d0

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Ada

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@blazoncek
Copy link
Collaborator

Can you, please, use exception decoder and provide decoded output?
You will need to compile sources yourself, preferably using debug options.

@Andro-Marian
Copy link
Author

Andro-Marian commented Aug 27, 2024

If you can help me with a guide on VSCode how to debug, because I already try and it was unsuccessful.

I will try when I wake up tomorrow.

@blazoncek
Copy link
Collaborator

Please use WLED forum or Discord for that. It has been answered many times before.

@Andro-Marian
Copy link
Author

@blazoncek
Copy link
Collaborator

From the crash dump you provided it can be seen that the crash happens in system libraries (WiFi UDP) during handleNotification().

handleNotification() is used if you have sync receive enabled and slave device listens for sync messages. I would suspect a rogue packet...

And BTW, please use 0.15 when submitting bugs. 0.14 will not receive updates any more and several bugs were fixed in 0.15 already.

@Andro-Marian
Copy link
Author

The Sync button is not activated. About that you say?

@blazoncek
Copy link
Collaborator

The Sync button is not activated. About that you say?

That button is for master aka sender. This is for slave aka receiver. It is always active but you can disable receiving by unchecking all receive groups.

@Andro-Marian
Copy link
Author

Andro-Marian commented Aug 29, 2024

Also, the 0_15 branch takes (41 seconds) than latest 0.15.0-b4 release to reboot.
All sync settings are unchecked.
0.150-b4 Release Source.txt

@blazoncek
Copy link
Collaborator

Again your crash dump shows abort from within system libraries (possibly OOM during network packet receive).

I urge you to use Wireshark and monitor network traffic to and from the ESP that is crashing.

There is of course a possibility that there is a memory leak somewhere within WLED but that is impossible to tell from these crash dumps.

@Andro-Marian
Copy link
Author

Andro-Marian commented Aug 29, 2024

I don't think is a network issue. Another use managed it to reproduce on discord.
And is only when setting the leds length below or equal to 3.
For my doesn't looks a network issue.

On the 0.15.0-b4 sometimes the crash happens after leaving the Fireworks 1D to Solid than on 0.14

Still crashes with WLED-AP connected with phone.
Crashes when scanning for Wi-Fi too.
Maybe this should be send to the Espressif.

@softhack007 softhack007 added the needs investigation The bug has not yet been reproduced by me. Analysis or more details are needed. label Sep 4, 2024
@softhack007 softhack007 added this to the 0.15.0-final candidate milestone Nov 2, 2024
@willmmiles willmmiles added confirmed The bug is reproducable and confirmed and removed needs investigation The bug has not yet been reproduced by me. Analysis or more details are needed. labels Nov 16, 2024
@willmmiles
Copy link
Collaborator

Reproduced on my test setup, investigating now

willmmiles added a commit to willmmiles/WLED that referenced this issue Nov 16, 2024
Attempt to allocate enough room for the "minimum" sparks; and ensure
that we never overrun the allocated array size.

Fixes Aircoookie#4120
softhack007 pushed a commit to MoonModules/WLED that referenced this issue Nov 17, 2024
Attempt to allocate enough room for the "minimum" sparks; and ensure
that we never overrun the allocated array size.

Fixes Aircoookie#4120
blazoncek pushed a commit to blazoncek/WLED that referenced this issue Nov 20, 2024
Attempt to allocate enough room for the "minimum" sparks; and ensure
that we never overrun the allocated array size.

Fixes Aircoookie#4120
@softhack007 softhack007 added the fixed in source This issue is unsolved in the latest release but fixed in master label Nov 22, 2024
netmindz pushed a commit that referenced this issue Nov 25, 2024
Attempt to allocate enough room for the "minimum" sparks; and ensure
that we never overrun the allocated array size.

Fixes #4120
@willmmiles
Copy link
Collaborator

Fix is merged in 0_15.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug confirmed The bug is reproducable and confirmed fixed in source This issue is unsolved in the latest release but fixed in master
Projects
None yet
Development

No branches or pull requests

4 participants