On Mon, Nov 2, 2020 at 8:06 AM gettimothy via Squeak-dev < squeak-dev@lists.squeakfoundation.org> wrote:

Hi Eliot,

Hi Timothy,

a few weeks ago debugging an issue raised by Andrei Chis I ran a test

runner in the simulator and the out of memory test it included caused the simulator to grow its central byte array to 17Gb. When I saved the image it was 34Gb. The workflow threw up a policy error. The VM would not shrink memory unless it had done a GC but once it had 17 Gb of free space it wasn’t going to do a GC. So I updated the vm and fixed the policy error and now the vm will happily shrink back after growing yo many gigabytes.

This is all just to point out that a match 3rd vm is a tad on the old side.

Thx, I will upgrade the VM ASAP.

BTW, how much ram do you have on your system?

.free -h total used free shared buff/cache available Mem: 6.7G 6.0G 225M 1.0M 506M 358M Swap: 0B 0B 0B

The vm will happily use all of it and more unless you set an upper bound on the size of memory (command line and vm parameter)

./squeak6.0alpha/bin/squeak --headless --memory 3000 squeak6.0alpha/shared/Squeak6.0alpha-19802-64bit.image &

is the command I use. I am not sure what the '3000' refers to, I am assuming it is 3G.

Now you can use "-memory 3g" and have no doubt. Note that "--" is Pharo, and "-" is Squeak.

_,,,^..^,,,_ best, Eliot