-
Notifications
You must be signed in to change notification settings - Fork 26
Memory leak with EGT demo? #33
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
Comments
Hello, This sounds quite different from the other issue that was about caching more and more images. Right now, we didn't observe it, but we didn't test it on such duration. We'll have a look as soon as possible. Thanks for reporting this issue. Regards, |
Ok thanks a lot, from our experience and our code issues, it seems connected to animations... |
Here a new log concerning another test we made during last weekend. This time we used EGT demo flashing kernel image 2022.07 |
Hello, We have not started the debugging yet. Thanks for your inputs. For sure, it will be useful. Regards, |
Hello do you have any news? |
Hello, Sorry, no, not yet. We are in the release process of 1.11, we'll have a look once the release is done. As it is sync with linux4microchip we can't postpone it. Depending of the fix, we'll release a 1.11.x or it will be in the 1.12. Regards, |
Ok, so we will have to wait about 3/4 month at minimum, right? |
I can't tell until we find the root cause. It can be due to EGT or other components used by EGT and even the LCD kernel driver. If it's related to EGT and if the fix is trivial, i.e. we don't expect side effects, we can release a 1.11.x so it could be done as soon as we find the fix. If it's more complex, it will be put on the master branch so you could cherry-pick it. It just means that the patch hasn’t yet passed all the tests we run before a release. We still have issues to fix for 1.11, I don't think we'll be able to really dig into this issue before June. |
Ok thaks a lot. |
Hello, We investigated more on the issue. We have not found any memory leak in process of the EGT application. Regards, |
Ok thanks a lot, you mean at least 2025.10 right? |
yes |
Is EGT version 1.11 still based on cairo? If so, on which version? |
Indeed, EGT 1.11 still depends on cairo; all references to cairo have been removed from the headers in the public API but internally, cairo is still used for the rendering when no GPU is available or when the render operation is not supported by the GPU. We didn't change the cairo requirement; in both CMakeLists.txt and configure.ac, we still require cairo >= 1.14.6 (the autotools support will be deprecated soon, we have moved to cmake). The actual version of cairo depends on the package in the build system, buildroot or yocto, used to generate the linux4microchip image. For instance, in buildroot for linux4microchip-2025.04, I see the version is set to 1.18.2 in the cairo package: package/cairo/cairo.mk in the buildroot-at91 repository (will move soon to buildroot-mchp). In yocto, still for linux4microchip-2025.04, in the openembedded-core repository, I see the meta/recipes-graphics/cairo/cairo_1.18.0.bb recipe, hence I guess, the cairo version should be 1.18.0. |
Thanks a lot. |
Uh oh!
There was an error while loading. Please reload this page.
Good Morning,
We encountered memory leak issues while implementing code using the EGT libraries. To ensure that the problem was not specific to our code, we tested the same scenario with the demo provided by the EGT libraries. Unfortunately, the memory leak persisted, indicating that the issue may lie within the libraries themselves.
In fact, flashing the NAND with the demo on SAM9x60-curiosity board, after 25/26 hours we encountered the same problem pointed out in #31, the EGT demo process was killed by the OOM-killer:
Do you have any suggestion regarding this? We are using 2024.10 buildroot based kernel
Thanks a lot and work well
The text was updated successfully, but these errors were encountered: