Charm++ parallel programming system

[Phil Miller <mille121 AT illinois.edu>]

Try adding prints to the constructor and destructor as well, and include the value of the 'this' pointer in all of them. I bet what you're seeing is copying of the message for each element receiving it.

On Tue, May 22, 2018 at 4:36 PM, James Bordner <jobordner AT gmail.com> wrote:

I'm trying to track down a memory leak related to creating chare array elements using a constructor that has a custom packed message argument.   I would expect the message's pack() and unpack()  methods not to get called if run on a single processor; however, they are not only called, but called multiple times per element inserted.  Specifically, pack(), unpack(), pack(), unpack(), unpack().  The chare array is derived from another base chare array, so perhaps that's causing the multiple pack()/unpack() calls.  But I don't know why the extra "unpack()" at the end, or why pack() and unpack() are getting called at all given it's a single processor run.

Thanks,

James