[Glass] SIXX load conflict

Dale Henrichs via Glass glass at lists.gemtalksystems.com
Thu Mar 5 10:05:42 PST 2015

On 03/05/2015 03:22 AM, Dario Trussardi via Glass wrote:
> Ciao,
> i nedd to load SIXX support into   GLASS   ( stone created 
> with development kit createTodeStone command ).
>> Mariano is correct that `onLock: [:ex | ex honor];` will eliminate 
>> the Warning, but I am suspicious that you are not running a recent 
>> version of GLASS.
>> You are getting a Warning during a topaz load (I assume ... in 
>> GemTools you would get a Warning dialog). There was a bug[1], where 
>> the wrong default action for a Warning was triggered during 
>> non-interactive loads and the bug was fixed back in June.
>> So I think you should upgrade GLASS1:
> i follow this :
>>   Gofer new
>>     package: 'GsUpgrader-Core';
>>     url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
>>     load.
>>   (Smalltalk at: #GsUpgrader) upgradeGLASS1.
> but into Gemtools and into topaz this code answer :
> ERROR 4067 , VM temporary object memory is full
> , almost out of memory, too many markSweeps since last successful 
> scavenge
> I setup  the relative to:
I'm not quite sure what is happening here ... I'm building a 
stone right now to see what might be happening, but it is worth noting 
that when you use createTodeStone, the GsUpgrader-Core package is loaded 
and you are updated to the very latest GLASS and tODE releases ...

With that said, it should also be safe to run GsUpgrader-Core scripts at 
any time ....

You've got a pretty large TOC so this is not easily explainable ...

I guess I'd like to see the actual gem/topaz log files ... to try to 
make more sense of this...


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150305/beb2e2ff/attachment.html>

More information about the Glass mailing list