Here's my issue:
I have an ASP.Net 2.0 application running on an XP sp3 development laptop (Pentium M 1.86GHz 2GB RAM) using an SQL Server 2000 database and the IDE is VS2008. This laptop has been used for 3 years and all software is up to date. The application runs without any issues on this laptop and there are no issues within VS2008...the application builds normally, no warnings or errors on build, and has been running in production (Windows 2003 server) for nearly 4 years.
Recently I began testing the application on a new laptop (i7-720QM Quad Core 1.60GHz 6MB 4GB RAM) running Windows 7 Ultimate, SQL Server 2005, and VS2008 targeting the 2.0 framework. The application builds without errors or warnings in the IDE and runs as expected on the laptop or when being debugged except:
- One page that is large (35,000+ lines of code) and produces a complex cost report is generating a "Cannot evaluate expression because the current thread is in a stack overflow state" error. The error occurs at different locations in the code even though the same data queries are being used to produce the report. Commenting out sections of the report only moves the error to another location! If enough code is commented out the page runs without error...and it doesn't seem to matter which code is commented out. If no code is commented out the error often occurs before the Page_Load event or just after the event begins.
Considering the application runs without problems on the XP laptop I have to think there is something going on with the new laptop's architecture...what I don't know and I'm not sure how to isolate this issue.