[Glass] Gemstone for OSX - VM temp obj space full when updating GLASS

James Foster James.Foster at GemTalkSystems.com
Wed Oct 2 16:03:02 PDT 2013

If you use Topaz, then the TempObjCacheSize is managed from the command line. If you use GemTools, then it is managed elsewhere and the the default TempObjCacheSize of 10 MB is much too small. In the screencast (https://www.youtube.com/watch?v=dnRB5rBbkiI) from 2:00 to 2:30 I demonstrate how to edit the config file so that it has a larger space. Basically, you need to edit ~/Library/GemStone/db1/etc/system.conf so that the last line is not commented out and has a larger value (say, 100 to 150 MB or 100000 to 150000 KB). 

At the moment you will need to edit this file after starting the database (we recreate the file each time we start). I plan to add the desirable TempObjCacheSize as a configuration that is managed through the app, but that isn't done yet.


On Oct 2, 2013, at 3:54 PM, Paul DeBruicker <pdebruic at gmail.com> wrote:

> I may have a setting wrong but if I start a new, initialize a GLASS  extent and begin to update GLASS to 1.0beta9.1  through GemTools I get a 
> "VM temporary object memory is full 
> , almost out of memory, too many markSweeps since last successful scavenge"
> error.  If I set the object cache to 1024 and the temp cache to 500 then it still happens.  What should I try next?
> Thanks
> Paul
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

More information about the Glass mailing list