-
Notifications
You must be signed in to change notification settings - Fork 166
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
Update AnimatedGIFs sketch for ESP32 to use malloc and avoid compile/startup issues with large buffers #69
Comments
if anyone needs this it's in my fork: https://github.com/marcmerlin/AnimatedGIFs |
I'm not sure where this stands after updating GifDecoder to use the AnimatedGIF library, so I'm going to close it |
if it still uses arrays instead of mallocs, the problem isn't fixed. |
OK, thanks for the clarification, I'll reopen it. |
I think this shows how to allocate the block needed for AnimatedGIF with malloc (after allocating mymemorypool with malloc): |
I'm only seeing the use of a single static array. If so, that is not as good as malloc as ESP32 has memory available at runtime with malloc but not available in pre-allocated buffers (global arrays). This is what I did to my old fork of the library, I switched everything to malloc.
I later updated mallocordie to allow allocating in PSRAM to further save main memory |
Thanks for the links, I'm not working on this now, but they look useful for later |
pixelmatix/AnimatedGIFs#26
The text was updated successfully, but these errors were encountered: