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

Track communication resource leaks #18

Open
ecpeterson opened this issue Nov 12, 2020 · 0 comments
Open

Track communication resource leaks #18

ecpeterson opened this issue Nov 12, 2020 · 0 comments

Comments

@ecpeterson
Copy link
Contributor

The communication manager is not especially good at tracking lost / leaked objects. Primarily, these include unanswered (and unanswerable) messages, as well as channels that are allocated and discarded without being released. Find a way to make these objects safer and to warn when they're misused.

The HASH-TABLEs held by a given COURIER might be converted to weak hash tables as supplied by TRIVIAL-GARBAGE. This would probably have the effect that unintended memory leaks are quietly covered up. Since detecting such leaks will be important for hardware implementations, covering them up is a worse option.

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