As a single thread extends itself by passing from feature to feature, your computer will set aside more and more memory.  If a thread is allowed to continue unchecked, there will come a time when your computer runs out of resources and abruptly terminates your project.  The point at which this happens depends largely on the amount of memory your computer has, but it is generally not a concern unless your project has synchronous connection paths that loop back on themselves. Such paths are referred to as re-entrant paths.

 

The good news is that this lurking threat can always be mitigated through the judicious use of feature outputs configured for asynchronous operation.  The Absyntax Editor will warn you when it detects re-entrant paths.  Note that Absyntax cannot know whether an input to any given feature will trigger an output.  Furthermore, if a re-entrant path is only executed a few times then it is unlikely to cause problems.  Thus the existence of a re-entrant path is not necessarily cause for concern.  Nonetheless it is considered good practice to eliminate these paths from your projects where practicable.