It's getting called from a TBB algorithm, but I don't see what
prevents us from getting unlucky, trying to modify the same
SparsityPattern::Row from two threads at once (working on two
different elements which share the same node), and trashing memory as
non-thread-safe STL operations conflict with each other.
---
Roy

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to