TaskManager bug re. RAMdisc allocation

New RAMdisc on a PMP system. RaspberryPi 256MiB. Repeatable.

Start with no RAMdisc.
Drag RAMdisc as far as you can to the right, to give it all available memory.
Something will probably crash.
RAMdisc will not be created, and all that memory will have “vanished”. (it’s in the RAMdisc DA).
As there is no RAMdisc, there is no obvious way to recover the memory.

Reason? I think something (Filer?) needs some memory to get itself running. Allocating all free memory to the RAMdisc does not permit this to happen. Things go avocado shaped.

Idea for a fix? Don’t permit all free memory to be allocated to the RAMdisc. Set aside a guard of, maybe, whatever the Next slot size is.

Technically this is a bug with whatever’s falling over, not a bug with the task manager :-)

But yes, this has been on my “to fix” list for a while, basically using the method you describe.

Maybe now that I’ve got the exception dump stuff in there I’ll be able to easily work out what stuff is falling over and why.