In reply to Nick.

I was quite surprised when my local WP instance tried to allocate over 6 exabytes. Glad it's fixed :)