r32248 should be the fix for this issue. I was overly optimistic about the cleanup of the classes. It turns out this is not possible without deep rearrangement of the class infrastructure. More info on the commit log.
Sorry for the mess, George. On Tue, Jul 15, 2014 at 11:38 AM, George Bosilca <bosi...@icl.utk.edu> wrote: > I'm also looking into it. > > George. > > > > On Tue, Jul 15, 2014 at 10:50 AM, Nathan Hjelm <hje...@lanl.gov> wrote: > >> On Tue, Jul 15, 2014 at 11:40:38PM +0900, Gilles GOUAILLARDET wrote: >> > r32236 is a suspect >> > >> > i am afk >> > >> > I just read the code and a class is initialized with >> opal_class_initialize >> > the first time an object is instantiated with OBJ_NEW >> > >> > I would simply revert r32236 or update opal_class_finalize and >> > free(cls->cls_construct_array); only if cls->cls_construct_array is >> not >> > NULL >> >> free(NULL) is safe. Something else is going wrong here. I am >> investigating. >> >> -Nathan >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: >> http://www.open-mpi.org/community/lists/devel/2014/07/15146.php >> > >
