I recently found this
and immediately remembered at least three instances where I fell for that bug.
Would it be possible to add some inspection to alert people to this quite unknown problem?
I am not sure how exactly the inspection should work...
Maybe simply trigger when an instance of Process goes out of scope without its streams properly closed?
Changed "ProcessBuilder" to "Process" - no idea what made me think of the wrong class name.