Man this was harder to track down than it should have been.
Would you try adding the line: SubFunctor::join(other); to the end of SortAndCopy::join, around generic_projector.h:1649? That seems to fix the problems I'm able to trigger easily; hoping it will fix yours too. I have to run and be AFK for a few hours but I'll put it into a PR tonight; it's a huge bugfix even if it turns out not to be the *only* bugfix we need. --- Roy On Thu, 16 May 2019, Alexander Lindsay wrote: > Awesome, thanks Roy. > > On Tue, May 14, 2019 at 2:36 PM Stogner, Roy H <royst...@ices.utexas.edu> > wrote: > > 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 > > > This message is from an external sender. Learn more about why this matters. > > _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
