distributedTriSurfaceMesh does not like having zero triangles on a processor
Summary
If a small surface gets used as a distributedTriSurfaceMesh it can happen that zero triangles end up on a processor. This upsets the local tree searching since it assumes there is at least on node on the tree.
Steps to reproduce
Example case
Run decomposePar & parallel snappyHexMesh (see the ./Allrun script). Exits with a sigsegv due to accessing out-of-bounds
Environment information
- OpenFOAM version : v2206
- Operating system :
- Hardware info :
- Compiler :
Possible fixes
Avoid local searching if no tree.