Juan Galvez

Note that this is not a common occurrence (usage of when buffers plus having undelivered messages in these buffers plus having these objects migrate). So this is considered low priority.

This seems like it is already supported, at least in the scenarios tested (see [forum topic](https://charm.discourse.group/t/running-hybrid-mpi4py-and-charm4py-programs-mpi-interop)). However, it would be good to test on different architectures, MPI implementations and use...

Not currently. But it is technically possible and would be a good feature to implement.

*Original date: 2017-02-06 19:02:11* --- Fix for cputopology mem leak: ~~https://charm.cs.illinois.edu/gerrit/#/c/2202/~~ https://github.com/UIUC-PPL/charm/commit/3a01bf56a793fd10a9bed631dfae7ad24b731c50 The mem leak in cldb is just something allocated at init that should be explicitly deleted at exit....

*Original date: 2017-09-18 14:37:21* --- I assume this issue refers to code inside Charm++? I don't quite understand your description of the issue with the previous code, but the new...

*Original date: 2017-10-11 20:23:18* --- Currently debugging this on Blue Waters.

*Original date: 2017-10-11 20:39:48* --- This is crashing on BW with 64 nodes. The dependency chain for building CkArray group is locMgr->mcastMgr->array. Apparently the crash is due to nodegroup dependencies...

*Original date: 2017-10-30 14:44:20* --- Respecting the dependencies during creation seems to solve problems. Performance still needs to be tuned. But nodegroup dependencies support does not exist yet in main...