On Thu, 16 Apr 2015, Harshad Sahasrabudhe wrote:
> I'm using MeshSerializer to serialize a mesh before output. The output > files turn out to be fine. When I try to destroy the MeshSerializer, it > gets stuck in the destructor on root process, while the code continues > executing on other processes. Here is the back trace on root process: > > > #6 0x00002ade0466328f in PMPI_Allreduce (sendbuf=0x7fffe6f30494, > recvbuf=0x7fffe6f30490, count=1, datatype=1275069446, op=1476395009, > comm=-2080374784) at ../../allreduce.c:1312 > #7 0x00002ade076eaeb8 in libMesh::ParallelMesh::parallel_max_elem_id() > const () from > /apps/group/ncn/carter/PETSc34/libs/libmesh/libmesh/.libs/libmesh_opt.so.0 > #8 0x00002ade076ea01b in > libMesh::ParallelMesh::update_parallel_id_counts() () from > /apps/group/ncn/carter/PETSc34/libs/libmesh/libmesh/.libs/libmesh_opt.so.0 > #9 0x00002ade076eb7cb in libMesh::ParallelMesh::delete_remote_elements() > () from > /apps/group/ncn/carter/PETSc34/libs/libmesh/libmesh/.libs/libmesh_opt.so.0 > > What is the correct way to destroy the MeshSerializer? Could you re-run in dbg or at least devel mode to see if we can get a more useful error message? Thanks, --- Roy ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
