The only leak worse than a memory leak is a submarine leak. Late last week we found a memory leak in the client/agent piece of SPM, our performance monitoring service. We fixed it immediately and published a new version of the SPM client. If you are an SPM user and if you have an SPM agent version 1.6.0 that was built before July 27, 2012, you may want to get the latest SPM client. We acted quickly to avoid having too many users affected by this, but luckily it appears this leak happens only on systems using Java 7. More precisely, we first spotted this leak in a production system running a 64-bit version of Java 7 update 5, the very latest version of Java as of this writing. We were able to reproduce this issue with Java 7, but have not seen it with java 6.
To check your SPM agent version:
# cat /spm/VERSION spm-1.6.0-solr-ubuntu Build date: Thu Jun 28 17:12:45 EDT 2012 Install date: Thu Jun 28 21:35:10 UTC 201
To check your Java version:
# java -version java version "1.6.0_31" Java(TM) SE Runtime Environment (build 1.6.0_31-b04) Java HotSpot(TM) Client VM (build 20.6-b01, mixed mode, sharing)
Please let us know if you have any issues or questions by emailing the secret spm-user mailing list or SPM support.