The Chrome plugin has a known limitation in that it opens a TCP connection on port 31924 locally and doesn't dispose of the connection once the process finishes execution:
http://portal.blueprism.com/customer-support/support-center#/path/1319712802
While I do appreciate the reasoning given in the Support Center article that this issue should only appear within the testing phase, it nevertheless has a big impact on project delivery, causing unnecessary slowdowns during the testing phase. [Additionally, it means terminal servers cannot be used at all, since one user/robot can block Chrome for everyone, even unintentionally] I would like for the TCP port to be closed once process execution is completed (within the Cleanup phase). Alternatively, being able to configure the port used could be an acceptable workaround.
... View more