Currently the lower-bound of the memory slider is the next power of two up from (initial+early).
This disallows setting 3gb max memory when initial+early is >2gb.
Expected behavior would be to allow a non-power-of-two lower bound, matching the upper-bound functionality.
Fixed on Win 7 64 and Ubuntu 14.04
OSX: When initial memory is set to 2048 and early generation is set to 1024, the slider will not slide lower than 4096. However, typing 3072 is allowed, and typing in any lower value sets it to 3072 when the user clicks save. This does not appear to be fixed.
<replace this line with the file content>
<replace this line with the file content>
OSX: When initial memory is set to 2048 and early generation is set to 1024, the slider will not slide lower than 4096. However, typing 3072 is allowed, and typing in any lower value sets it to 3072 when the user clicks save. This does not appear to be fixed.
i thought that was intended behaviour and the slider jumping to 4096 as a power of 2 correct
the memory setting gets update to 3072 automatically without thouching the slider.
will ask back if this was intended.
With initial + early generation >= 2GB, the slider will not slide below the next power of two. Below 2 GB, it will slide down to a value equal to initial + early generation. Whichever behavior is intended, something is inconsistent.
This is incorrect behavior.
The slider should always snap to the lower bound, the powers of 2 in between, and the upper bound.
The next build fixes the broken use case of (2048+1024) initial+early not snapping to the 3,072 lower-bound. The math is also easier to read now, and slightly faster.
As i've changed the math, please verify that snapping to the upper-bound still works!
(both capping at the memory ceiling, and snapping up to it)