On Mon, 13 May 2019, Alexander Lindsay wrote:
> I could maybe think of a libmesh-only case, but if you're willing to > run MOOSE, you can run the > moose/test/tests/geomsearch/nearest_node_locator/nearest_node_locator.i > input file. It appears to reproduce the error every time (with > --n-threads=2). I'm definitely managing to trigger libmesh-only errors with threaded projections too, and the assertion failure I'm getting is more helpful than that helgrind error, so I'm working from that angle first; when I get a patch ready I'll let you know and if it doesn't fix your case too then I'll try reproducing with MOOSE next. Thanks, --- Roy _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
