Lower that 8192 or use lower resolution imagery.
In your case, it's using 4m, 2m, 1m, and half meter imagery to try to build an image at 8192m resolution.
This means that each pixel on the 8192m resolution is corresponding to 4194304 (2048x2048) 4m pixels, 16777216 (4096x4096) 2m pixels, 67108864 (8192x8192) 1m pixels, and 268435456 (16384x16384) half meter pixels. Each tile is created from 65536 (256x256) pixels. Altogether, that's 23,364,622,090,240 (23 trillion) pixels where each pixel takes up around 4 bytes so 93,458,488,360,960 (93 TB of RAM). The work images now are bounded to the extents of the source imagery so it's probably not quite that large but still frighteningly large. If you had images in 2 different sections, you'd have problems.
The next IMC is programmed so it doesn't create work images but down sampling this far is still not suggested as you'd have to cache your entire imagery dataset to generate 1 tile.