On May 28, 2013, at 2:07 PM, Derek Gaston <fried...@gmail.com> wrote:
> Any ideas on stuff they can do to mitigate this? It's not clear to me that it is a singleton issue from the trace - is that problem inside the communicator constructor? But anyway, a workaround for the Singleton auto-construction is to make sure the remote_elem got built and instantiate it if not, c.f.: https://github.com/libMesh/libmesh/commit/7fabc7a93b6528128529e907372fa13a99093242 -Ben ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
