Yes, its enabled. I have a check to see if the buffer gets allocated or not.
After going through multiple threads and solutions on the forum, as well as existing issues in the repository, I was able to resolve my problem through trial and error.
The root cause of the screen issue was the use of a single API: lv_obj_set_style_transform_scale. I was using this function to scale down image-based containers to specific sizes across multiple screens. However, I noticed that it was consuming a significant amount of memory when I enabled logging at the INFO and TRACE levels. The logs showed unusual memory allocationsāsome layers were taking up 8KB, others 16KB, and some even 23KB.
I also found a related ticket in this repository, but it didnāt help in my case. Eventually, I resolved the issue by using pre-scaled images (resized them via editor) at the exact required sizes and completely removing lv_obj_set_style_transform_scale from all screens. Not only did this fix the display issue, but it also allowed multiple screens to initialize correctly, whereas previously, they were failing to do so.
I hope this helps anyone facing a similar issue, but Iād appreciate any insights into why this API was causing such high memory usage.