Yes. The traceback indicates that the visualization step, rather than necessarily the COSMO calculation itself, which is what is exhausting memory. QuantumATK is trying to construct an intermediate array of roughly 740 GiB.
There may be a way to work around this by accessing the COSMO surface/tessera data directly from the QuantumATK Python API and writing it to a more suitable format, but the exact approach depends on your QuantumATK version and on which COSMO object/calculator produced the surface.