[Glass] SIXX load conflict

[Dario Trussardi via Glass]

Dale,

> Dario,
> 
> I did a fresh createTodeStone using the latest gsDevKitHome release (SHA: 8fdc73fb176cf7e0ce33ad7d21eb448ba94ef5a6) and running the GsUpgrader-Core load multiple times does not run out of memory ..

I do test in a new clean tODE stone.   All works fine without error.

In the stone where the system erase the out of memory error   i loaded :

GsDeployer
  bulkMigrate: [ 
    {#('Seaside3' '3.0.13' 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main').
    #('ZincHTTPComponents' '1.1' 'http://www.squeaksource.com/ZincHTTPComponents').
    #('Magritte3' '3.0' 'http://www.squeaksource.com/MetacelloRepository').
    #('Magritte3AddOns' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository').
    #('Pier3' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository').
    #('Pier3AddOns' '3.0.3' 'http://www.squeaksource.com/MetacelloRepository')}
      do: [ :ar | 

No other things. 

Today i resubmit the  (Smalltalk at: #GsUpgrader) upgradeGLASS1  into the stone incriminated

and fork fine without error.

> . so I will need to see some log files to figure out what might be going wrong...

What i need do to use the latest gsDevKitHome release ?

I need to do	 git pull   command into gsDevKitHome  before create a new tODE stone?

Ciao, thanks,

	Dario
> 
> Dale
> 
> On 03/05/2015 10:05 AM, Dale Henrichs wrote:
>> 
>> On 03/05/2015 03:22 AM, Dario Trussardi via Glass wrote:
>>> Ciao,
>>> 
>>>  i nedd to load SIXX support into   GLASS 3.1.0.6   ( 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:
>>> SHR_PAGE_CACHE_SIZE_KB = 2000000;
>>> GEM_TEMPOBJ_CACHE_SIZE = 1900000;
>>> 
>> I'm not quite sure what is happening here ... I'm building a 3.1.0.6 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...
>> 
>> Dale
>> 
>> Dale
> 
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

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