esp32-8048S070C Slowing becoming unresponsive

[lesintheusa]

Firstly What a great Project I love it :) How do I contribute some cash to say Thank you.

The problem I am experiencing is when I run only the LGVL Portion nothing else.
At startup, it works fine. However gradually over time the CPU usage drops gradually and after about 12 hours the CPU% is around 1% and the display becomes unresponsive.
Is there a setting I am missing or is it a bug?
I am using Squareline to Create my screens and placing the Squareline code in the UI folder.

Best Regards Les

[rzeldent]

Hi Les,

You're using the demo application?

This sounds like a memory leak. However, there is also the LVGL memory usage on the left.
I suggest to add logging to display the available memory so this can be ruled out....

This logging is already present in the startup() function.
So write down the free memory at the start and display this again in the loop() function.

[lesintheusa]

Dear Sir, I went back to the original demo and it ran perfectly fine. Gradually adding I discovered that the slow came from the nimBLE library. Turns out that if your scanning with nimBLE everything slows down as it is a CPU hog. Which is not good because I want to use the display for temperature form Ruuvi tags. I also noted that using on change to update the lvgl tags can cause the LVGL to become unresponsive or panic crash reset. I moved the LVGL commands into main and as long as I am not sanning too often the problem is fixed. It would be nice if it could be possible to equalize the priority of the scan it is calimed not blocking but it is a CPU hog. Again thanks for building this awesome library do you have a go fund me or something I should like to contribute something. Best Regards Les

…

On Tue, May 7, 2024 at 12:41 PM Rene ***@***.***> wrote: Hi Les, You're using the demo application? This sounds like a memory leak. However, there is also the LVGL memory usage on the left. I suggest to add logging to display the available memory so this can be ruled out.... This logging is already present in the startup() function. So write down the free memory at the start and display this again in the loop() function. — Reply to this email directly, view it on GitHub <#166 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQQUMT55EMR7XETHZKM4RXDZBEG3TAVCNFSM6AAAAABHLIB2U2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYHE3TMMJWGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[rzeldent]

Hi Les,

Nice to hear that the issue is resolved. I think the issue can be closed?