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

Memory leak #1

Open
supercamel opened this issue May 8, 2023 · 0 comments
Open

Memory leak #1

supercamel opened this issue May 8, 2023 · 0 comments

Comments

@supercamel
Copy link

pico_flash_write() assigns memory to stored_value using a call to malloc. Later it assigns stored_value the result of pico_flash_read() without freeing stored_value first.

To be honest, I don't think a library like this shouldn't need to call malloc/calloc at all. Instead just require the user to provide the necessary memory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant