Stream tracer with custom source seeding bug

I’m afraid I can’t give you a state file that will show you the behavior right away. However I’m sure you can provoke it on your side:
Start 8 pvservers, load the attached state file (uses the data from previous post). The state has just one StreamTracerWithCustomSource filter and it will probably load without problems. Keep adding more StreamTracerWithCustomSource filters to the pipeline by using the MaskPoints2…8 as seeding elements. At some point you will notice streamlines which are broken/interrupted, the previously shown wrong seeding location or what always happens on my side at some point: ParaView will crash even there is plenty of memory left on both sides, server and client.

Let me know if this works for you.
state_streamlines.pvsm (2.6 MB)