When using the Crystal .NET runtime, has the SAP OEM team seen an issue where the prowin32.exe sessions are taking up large amounts of memory over a period of time when using Crystal reports?
http://knowledgebase.progress.com/articles/Article/P123672
What typically is the acceptable memory usage level and/or range for the prowin32.exe sessions when using Crystal reports?