|
it
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Memory Leak with classic asp
Hi,
Anyone have any insights on how to debug a memory leak with a classic asp application? Any thoughts would be appreciated. thanks! Bill =?Utf-8?B?QmlsbDQ0MDc3?= wrote on 01 mrt 2006 in
microsoft.public.inetserver.asp.general: > Anyone have any insights on how to debug a memory leak with a classic Perhaps write a better script?> asp application? Any thoughts would be appreciated. > -- Evertjan. The Netherlands. (Please change the x'es to dots in my emailaddress) I wish :(
Seems I've inherited a classic asp application with several ten's of thousands lines of code... with a memory leak... Bounds Checker only works with managed code... and constructive insight would be greatly appreciated. thanks, Bill Show quote "Evertjan." wrote: > =?Utf-8?B?QmlsbDQ0MDc3?= wrote on 01 mrt 2006 in > microsoft.public.inetserver.asp.general: > > > Anyone have any insights on how to debug a memory leak with a classic > > asp application? Any thoughts would be appreciated. > > > > Perhaps write a better script? > > -- > Evertjan. > The Netherlands. > (Please change the x'es to dots in my emailaddress) > =?Utf-8?B?QmlsbDQ0MDc3?= wrote on 02 mrt 2006 in
microsoft.public.inetserver.asp.general: > "Evertjan." wrote: [please do not toppost on usenet]> >> =?Utf-8?B?QmlsbDQ0MDc3?= wrote on 01 mrt 2006 in >> microsoft.public.inetserver.asp.general: >> >> > Anyone have any insights on how to debug a memory leak with a >> > classic asp application? Any thoughts would be appreciated. >> > >> >> Perhaps write a better script? > I wish :( I do not think ASP pages should have that many lines, > > Seems I've inherited a classic asp application with several ten's of > thousands lines of code... with a memory leak... Bounds Checker only > works with managed code... and constructive insight would be greatly > appreciated. so my idea still stands. Try to devide the problem, giving the user intermediate results. And look for unnecessary repeats, string concatenations and executions in loops. Perhaps the amount of memory needed runs out? Then set breakpoints: debug = true ...... if debug then response.write "bp 17: " & a &" " & b : response.end -- Evertjan. The Netherlands. (Please change the x'es to dots in my emailaddress) Bill44077 wrote:
> Hi, The people over at .inetserver.iis might be able to provide more assistance.> > Anyone have any insights on how to debug a memory leak with a classic > asp application? Any thoughts would be appreciated. > There's a tool called IISState that I often hear about ... -- Microsoft MVP -- ASP/ASP.NET Please reply to the newsgroup. The email account listed in my From header is my spam trap, so I don't check it very often. You will get a quicker response by posting to the newsgroup. Thanks Bob - I'll give it a try!
Show quote "Bob Barrows [MVP]" wrote: > Bill44077 wrote: > > Hi, > > > > Anyone have any insights on how to debug a memory leak with a classic > > asp application? Any thoughts would be appreciated. > > > The people over at .inetserver.iis might be able to provide more assistance. > There's a tool called IISState that I often hear about ... > -- > Microsoft MVP -- ASP/ASP.NET > Please reply to the newsgroup. The email account listed in my From > header is my spam trap, so I don't check it very often. You will get a > quicker response by posting to the newsgroup. > > > "Bill44077" <Bill44***@discussions.microsoft.com> wrote in message What exactly do you want to debug?news:53973A75-3982-4D66-BD71-4BB99DAE0865@microsoft.com... > Hi, > > Anyone have any insights on how to debug a memory leak with a classic asp > application? Any thoughts would be appreciated. A COM component? Or just script? What language? It's kind of a combination of things including
classic asp with vb script using a sql db a couple more recent written vb.net and c# components At this point we have no idea where the memory leak is occuring - although it seemed to have appeared when the app was migrated from W2k to W2k3. We've talked about running in IIS5.0 compatibility mode to see if the problem goes away. But it could be load related. thanks, Bill Show quote "Egbert Nierop (MVP for IIS)" wrote: > > "Bill44077" <Bill44***@discussions.microsoft.com> wrote in message > news:53973A75-3982-4D66-BD71-4BB99DAE0865@microsoft.com... > > Hi, > > > > Anyone have any insights on how to debug a memory leak with a classic asp > > application? Any thoughts would be appreciated. > > What exactly do you want to debug? > A COM component? > Or just script? > What language? > > > "Bill44077" <Bill44***@discussions.microsoft.com> wrote in message If you want to debug manually, (with step-trace) you can attach visual news:8D061581-5709-457B-BB10-0D97A1165901@microsoft.com... > It's kind of a combination of things including > > classic asp with vb script using a sql db > a couple more recent written vb.net and c# components > > At this point we have no idea where the memory leak is occuring - although > it seemed to have appeared when the app was migrated from W2k to W2k3. > We've > talked about running in IIS5.0 compatibility mode to see if the problem > goes > away. But it could be load related. studio to W3WP.exe, the correct process that hosts your site. put source code and .pdb files in your website as well. Just put some System.Diagnostics.Debugger.Break(); statements in components that you want to view. But the best way, is to test components one by one. How? Have one classic asp run one c# component and run it using a http load emulator.  |
|||||||||||||||||||||||
Other interesting topics