If they could enhance logging during the cooking process, e.g. showing which assets are being processed, then we could most likely figure out which asset(s) are causing it to be going out of memory & resolve it ourselves.
This is a repeating pattern I recognized, lack of meaningful logs to resolve issues ourselves.
I’m now merely guessing which assets are causing the OOM and hopefully I can resolve it this way.
My post: Launch session - Cook failure out of memory - #6 by L10NHEART