I've experienced multiple kernel panics trying to create a model with latent space of 64w-96h.
I was able to do this without much problems when --attention-implementation ORIGINAL was used and was able to output the correct image. However, when SPLIT_EINSUM is used I'll get kernel panics. This will happen when setting the flag in python --check-output-correctness but it will also happen in the swift CLI.
Again, I was able to get this to work with ORIGINAL and not setting .all but setting .cpuAndGPU. I'm on a M1 Max with 64gigs memory. If set to .all with the ORIGINAL attention, the program will crash.
I've experienced multiple kernel panics trying to create a model with latent space of 64w-96h.
I was able to do this without much problems when
--attention-implementation ORIGINALwas used and was able to output the correct image. However, whenSPLIT_EINSUMis used I'll get kernel panics. This will happen when setting the flag in python--check-output-correctnessbut it will also happen in the swift CLI.Again, I was able to get this to work with ORIGINAL and not setting
.allbut setting.cpuAndGPU. I'm on a M1 Max with 64gigs memory. If set to.allwith the ORIGINAL attention, the program will crash.