[squeak-dev] Re: #'insufficient object memory' in Spur

Chris Muller ma.chris.m at gmail.com
Fri Nov 14 20:40:00 UTC 2014


I was already using the 10/28 image.  Ah ha!  It seems I accidently
Load'ed that latest System package (unconverted) instead of Merge'ing
it..  OOPS!  Not my day today!

On Fri, Nov 14, 2014 at 2:26 PM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> Hi Chris,
>
> On Fri, Nov 14, 2014 at 7:43 AM, Chris Muller <ma.chris.m at gmail.com> wrote:
>>
>> Hi Eliot, thanks a lot for your help on the CM header.  I decided to
>> try to add a new bit indicator in my CompiledMethodBuffer (pickled
>> state of a CM) to indicate which header format it was pickled in so I
>> can hopefully maintain a heterogeneous environment.
>>
>> Now, maybe I goofed up my image while testing it at some point because
>> I cannot seem to allocate a 50MB ByteString (even though (Smalltalk
>> vmParameterAt: 3) reports just 89,627,904)
>>
>>    String new: 50000000
>>
>> causes a failure in primitve 71, which causes the failure code to run,
>> which sends #growMemoryByAtLeast: to Smalltalk.  But, there are no
>> implementors of #growMemoryByAtLeast: in the image..!
>
>
> If you download a recent Spur image from my web site you'll find it
> there-in.
>
>>
>>
>> Do you have an impl. of that method?  This could be a real problem for
>> me to move to Spur because I absolutely depend on handling OutOfMemory
>> errors to build my large models..
>
>
>
>
> --
> best,
> Eliot


More information about the Squeak-dev mailing list