https://bugs.winehq.org/show_bug.cgi?id=32316 --- Comment #15 from Bruni <earns.61(a)gmail.com> --- Anastasius, Microsoft says that debugging an app which requires a lot of memory (>800 MB), as such, may cause OutOfMemoryException: https://docs.microsoft.com/en-us/archive/blogs/webtopics/troubleshooting-sys... ==quote== There are two reasons why you might see an OOM condition. Your process is using a lot of memory (typically over 800MB.) The virtual address space is fragmented, reducing the likelihood that a large, contiguous allocation will succeed. It's also possible to see an OOM condition due to a combination of 1 and 2. Let's examine some of the common causes for each of these two reasons. Common Causes of High Memory When your worker process approaches 800MB in private bytes, your chances of seeing an OOM condition begin to increase simply because the chances of finding a large, contiguous piece of memory within the 2GB address space begin to decrease significantly. Therefore, you want to avoid these high memory conditions. ==quote== When you're developing and debugging an application, you will typically run with the debug attribute in the web.config file set to true and your DLLs compiled in debug mode. However, before you deploy your application to test or to production, you should compile your components in release mode and set the debug attribute to false. ==quote== -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.