The test could be changed to run ONLY if the vm was started with a limiting
-memory argument.  See the attached method, Smalltalk>>#imageMemoryLimit.
Let THAT be the way to enable the test, that the user started the image in
a way that doesn't allow it, even accidentally, to swallow up the whole
system.

Best,
  Chris


On Wed, May 18, 2022 at 11:07 PM Lauren Pullen <drurowin at gmail.com> wrote:

> Hi list,
>
> I can't remember if I already asked this, please ignore if it's a double.
>
> AllocationTest's testOutOfMemorySignalExtreme is too disruptive to the
> rest of the OS to run by default.  It will absolutely fill my hard drive
> with pagefile if the OS doesn't trap and ask me to start terminating
> processes first.  If the pagefile fills the hard drive many programs are
> simply incapable of not corrupting their persisted state... every time
> it happens I need to go through and delete preferences and cache
> folders.  The test has never completed, and I lack a 1 TB hard drive or
> unused ones to RAID together.
>
> I feel it's appropriate to disable that test and require users
> explicitly allow it to run.  Personally, I delete the method.  Can this
> be disabled?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220531/0cca3c62/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SmalltalkImage-imageMemoryLimit.st
Type: application/octet-stream
Size: 1095 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220531/0cca3c62/attachment.obj>