Occasionally I attempt to save a document that appears to hit the memory limits of its docker container. When this happens, the CPU spikes but the save command never completes. When I modified my code to include new DocSaveOptions() { MemoryOptimization = true } in the save command, it lowered the memory usage so that the command could complete. This should help prevent the issue but it would be nice if the save command could throw an OutOfMemory exception or something similar so that I could detect these instances. Ideally I could try saving without memory optimization enabled for speed. Then only if it fails, catch it and save with memory optimization enabled.
Have you tried the latest (21.2) version of Aspose.Words for .NET on your end? In case the problem still remains, then please ZIP and upload your input Word document you are getting this problem with here for testing. We will then investigate the issue on our end and provide you more information.