1.6.1 final readme changes

diff --git a/docs/dist/doc/README-161.html b/docs/dist/doc/README-161.html
index 35b58ea3b73485a43112a0357fb13f0e5be6693a..e71b6643aca0ae9867618168348ebfd05077fc7f 100644 (file)
--- a/docs/dist/doc/README-161.html
+++ b/docs/dist/doc/README-161.html
@@ -100,10 +100,15 @@ weaver instance correctly matched the lifecycle of the associated classloader.
 Here is a memory usage graph for AspectJ1.6.1 - this shows an application that spawns 7 threads which run continuously for a few minutes.  Each thread
 repeatedly creates a classloader, weaves 500 classes using it then discards the classloader.  You can see that over time the memory is recovered
 correctly and when all threads complete (and all classloaders are orphaned), all the weavers are discarded.
+
+<p>First, AspectJ 1.6.0, in which memory was never correctly recovered and so an OutOfMemory problem would always occur eventually.
+<center>
+<img src="memLtwStress_160.PNG"></img>
+</center>
+<p>And now AspectJ 1.6.1:
 <center>
 <img src="memLtwStress_161.PNG"></img>
 </center>
-<p>In 1.6.0 the memory was never correctly recovered and so an OutOfMemory problem would always occur eventually.
 
 
 <h2>Incremental compilation</h2>

diff --git a/docs/dist/doc/memLtwStress_160.PNG b/docs/dist/doc/memLtwStress_160.PNG
new file mode 100644 (file)
index 0000000..dbf46c0
Binary files /dev/null and b/docs/dist/doc/memLtwStress_160.PNG differ