Currently using PL/SQL Developer V13, and the issue still exists.
Is there a fix for this, and if not maybe some explanation?
Is it necessary for the connected user to have ALTER SESSION privilege? because this is required to use the workaround to open another PL/SQL Developer instance and kill the rogue test session.