I’ve seen many posts online regarding this issue, and there are many suggestions offered. From increasing the default limit size, to ensuring your properly disposing these documents. Fortunately, there’s a quick fix for this issue, that will allow you to get up and running immediately, which is recycling the App Pool for your application. Your app pool maintains the temporary document space for these documents, and if there is a memory management issue, it will be here.
This was the best case scenario for getting Crystal working immediately on my end, and I will probably deploy an update to an app in requirements of this document format to ensure proper document disposal. I don’t see a huge necessity in doing so, since the application has been in full swing for over a year, and has only ran into this error once, but it’s always best to write for all case scenarios.