charm AT lists.siebelschool.illinois.edu
Subject: Charm++ parallel programming system
List archive
- From: James Bordner <jobordner AT gmail.com>
- To: charm <charm AT lists.cs.illinois.edu>
- Subject: [charm] Packed messages in Chare constructors
- Date: Tue, 22 May 2018 14:36:05 -0700
- Authentication-results: illinois.edu; spf=pass smtp.mailfrom=jobordner AT gmail.com; dkim=pass header.d=gmail.com header.s=20161025; dmarc=pass header.from=gmail.com
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
- [charm] Packed messages in Chare constructors, James Bordner, 05/22/2018
- Re: [charm] Packed messages in Chare constructors, Phil Miller, 05/22/2018
- Message not available
- Re: [charm] Packed messages in Chare constructors, James Bordner, 05/24/2018
- Re: [charm] Packed messages in Chare constructors, Phil Miller, 05/24/2018
- Re: [charm] Packed messages in Chare constructors, James Bordner, 05/24/2018
- Message not available
- Re: [charm] Packed messages in Chare constructors, Phil Miller, 05/22/2018
Archive powered by MHonArc 2.6.19.