Hi Chris. We found a problem with WeakOrderedCollection in Pharo which may cause problems in Magma users in Pharo. Basically, once a WeakOrderedCollection needed to #grew, it stops being weak because the internal array was replaced by a Array instead of a WeakArray.  <br>
<br><pre>(WeakOrderedCollection new instVarNamed: &#39;array&#39;) class -&gt;&gt;&gt;&gt; WeakArray 
 

(WeakOrderedCollection new grow instVarNamed: &#39;array&#39;) class  -&gt;&gt;&gt;&gt; Array</pre><br>So....I can imagine that some applications running magma may grow a lot due to this bug.<br>
<br>Just to check whether someone is having this bug or not, you may want to execute:<br clear="all"><br>WeakOrderedCollection allInstances select: [:each | (each instVarNamed: &#39;array&#39;) class = Array ]<br><br>if you have instances, then that&#39;s a problem ;)<br>
<br>To fix it, you can fileine the changes of the issue tracker: <br><a href="http://code.google.com/p/pharo/issues/detail?id=4596">http://code.google.com/p/pharo/issues/detail?id=4596</a><br><br>and then you should fix the already created instances. <br>
<br>cheers<br><br>ps: I have no idea how much Magma uses WeakOrderedCollection, but I thought it was just worth it to raise a warning.<br><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br>

<br>