Okay, that still might be the pool size.
I will do a debugging session locally a bit later today to try to patch this. I will get back to you tomorrow as soon as I find the issue with the pool sizes and why it needs so much memory, there must a be a bug there.
Either way, if I find the issue then I will send you a patched version or instructions on how to get around it by tomorrow.