Skip to content

Reclaiming Memory #3279

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

Closed
zephyrbot opened this issue Mar 2, 2017 · 1 comment
Closed

Reclaiming Memory #3279

zephyrbot opened this issue Mar 2, 2017 · 1 comment
Labels
area: Kernel Enhancement Changes/Updates/Additions to existing features priority: high High impact/importance bug

Comments

@zephyrbot
Copy link
Collaborator

zephyrbot commented Mar 2, 2017

Reported by Robert Beatty:

As a developer I would like to be able to allocate and reclaim memory so that I can kill a task or thread and be able to re-claim the memory.

(Imported from Jira ZEP-1831)

@zephyrbot
Copy link
Collaborator Author

by Robert Beatty:

"Previous viper this was not supported, however, Zephyr now has support for MALLOC and dynamic alloc."

Anas Nashif to check: If a task is killed, can I reclaim memory?

@zephyrbot zephyrbot added priority: high High impact/importance bug area: Kernel Enhancement Changes/Updates/Additions to existing features labels Sep 23, 2017
This was referenced Sep 23, 2017
@nashif nashif closed this as completed Feb 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Kernel Enhancement Changes/Updates/Additions to existing features priority: high High impact/importance bug
Projects
None yet
Development

No branches or pull requests

2 participants