GCP Issue 9 - memory leak #6
Description
Reported by kab...@gmail.com, Jul 1, 2010
There is a memory leak in the spawn command.
The current Expect4j class is associated with each new spawnId via interp.setAssocData, but never cleared.
This leads to a memory leak, if we spawn a lot in the same session.