[bechols97]

This is a bugfix to add cleanup functions for resources.

The Hip and Cuda resources are non-owning and never destroy streams, which show up as leaks in memory checkers/sanitizers. In these cases, the streams would be destroyed in the new cleanup function. If there is no cleanup needed for a resource (such as Host, Omp_target, Sycl), then the cleanup function will be a no-op.

An open question for this PR is whether the cleanup functions should be thread-safe? Currently, these are not thread safe to be consistent with RAJA::release_unused_internal_memory().

Note: These changes were created by AI. I have reviewed the changes and they seemed reasonable.
At this point, this has been redesigned from the initial changes made by AI.

Related to: #223

[artv3]

Will we need a patch release ? We use the wait_for functions in my application, wait_for(default_res) type of calls.

[bechols97]

No, we probably don't need a patch release for these changes. With these changes, applications will realistically be calling the cleanup function only once prior to exiting since the number of streams created within the lifetime of the program is constant and will only be reported as leak by memcheckers/sanitizers during exit. In the worse case, this includes camp's default stream and 16 additional streams if applications use more than the default stream.

Regarding the wait_for question, I believe events were made owning in #206, which was in the release.

[rhornung67]

Seems reasonable to me. However, someone else should review and approve to make sure.

[rhornung67]

@bechols97 @MrBurmark this branch of Camp passed all the CI checks in RAJA. Please feel free to merge it. After that, I will put up a PR for the Camp patch release.