 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Visual Studio.NET / IDE / December 2004Hang while debugging ASP.Net on Windows 2003
Hi, ENV: Windows 2003 Enterprise, Devstudio 2003, .Net framework 1.1, Office 2003 SP1 Since applying the Visual Studio/Office/Windows hotfixes for the JPEG issue, I am having problems debugging an ASP.Net application. Visual Studio will hang and consume anywhere from 10% to 90% CPU when starting debugging of an ASP.Net application. This happens when either starting the debugger from the IDE or attaching to the w3wp.exe process. Looking via task manager, the devstudio.exe process is simply spinning CPU cycles - there is no change in memory usage. This happens frequently, but intermittently. If it helps, when attaching to the w3wp.exe process, the point at which devstudio hangs is almost instantly after I hit "OK" on the "Attach to process" dialog. The IDE does not refresh after that point or show any indication it has attached successfully. The ASP.Net application is running in IIS6 native mode under the default application pool identity (NETWORK SERVICE). This has never happened before to me or my colleagues (who haven't applied the patch yet). Whether it was the JPEG fix or another hotfix, I don't know. I can't obtain any more hotfixes as the Windows Update web mechanism hangs at 66% detecting... :) Do you have any suggestions? Please let me know if you need tracing etc. Thanks, Stuart Some additional information: When starting the debugger through the IDE (setting the ASP.Net app as the startup project with a start page), the IDE doesn't get as far as launching IE... The debugging environment is switched to (Call stack, variables, thread windows appear), but then nothing. Dragging windows over the top of Visual Studio cause the frames to be repainted, but you only see the docked window titles. There is no content rendered in any of them, only a white or grey background. I would post a screenshot, but the state it is in means that it can't be captured. I've left the hung instance for a little over 3 hours now and still nothing. > Hi, > [quoted text clipped - 28 lines] > Thanks, > Stuart Hi Stu, As the problem you mentioned, does it occur on all the ASP.NET web projects on that machine? Even when we creating a new web project on it? Is it ok to run the web application if we use CTRL + F5 to launch the application or directly in Internet explorer. In addition, is there any ANTI-VIRUS softwares installed on your machine? There is a known issue that the Anti-virus software on the machine will make the VS.NET hang when debugging asp.net web application. Please have a check on the above things. If you have any other questions or any new findings, please feel free to post here. Thanks. Regards, Steven Cheng Microsoft Online Support  SignatureGet Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.) Hi Steven I cannot reproduce it on another - simpler - ASP.Net project (tried about 10 times launching the project in debug mode (F5) after slight code changes everytime), but that is not to say that it won't happen :) The project I see the problem with is relatively complex, but nothing has changed in terms of project configuration apart from addition of 2 more .Net references. Running the project using CTRL-F5 hasn't caused a hang. I have Antivirus software installed, but I've had that for that last 3 years - nothing has changed there. I see that someone else has also reported the same issue. It is frustrating to say the least because I have to kill devstudio and then restart it, load the solution (which is large)...5 minutes in all, just so that I can restart debugging, but 4 or 5 builds later, it might happen again. Stu > Hi Stu, > [quoted text clipped - 17 lines] > (This posting is provided "AS IS", with no warranties, and confers no > rights.) Hi Stu, Thanks for your response. Since you mentioned that the problem is specified on the particular project, it dosn't seems to be the anti-virus issue. But I still recommend you stop the anti-virus tool and have a try:) Also, since the VS.NET will create a local cache for every web project under the {sys dir}:\Documents and Settings\user\VSWebCache\SITE\project name You may try deleting this folder to see whether it helps. In addition, Since the problem not occur on the other projects, I suggest you also try creating a new project and move all the items to the new project step by step and test whether any particular part of the project will cause the problem. If you have any other questions or findings, please feel free to post here. Thanks. Regards, Steven Cheng Microsoft Online Support Hi Stu, Have you had a chance to check the things in my last reply or have you got any further progress on this issue? If there is anything else we can help, please feel free to post here. Thanks. Regards, Steven Cheng Microsoft Online Support SignatureGet Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.) Hi Steven, I disabled the AntiVirus realtime scan and also deleted everything in the VSWebCache folder but I'm still seeing it. I can't try moving the files to a new project and seeing which, if any, cause the problem because of the permutations involved and the dependencies between projects in our solution, which means all or none must be moved! Out of interest, has Microsoft had any other reports of this (apart from the other poster in this thread)? Thanks, Stu > Hi Stu, > [quoted text clipped - 11 lines] > (This posting is provided "AS IS", with no warranties, and confers no > rights.) Hi Stu, Thanks for your response. I've also checked some former issues and also the threads in google, but the scenario seems different from yours. Such as , anti-virus, installed beta version of VS.NET or some other patchs for win2k. Since you mentioned that the problem only occurs after you installed the JPEG issue's hotfix and other colleagues who haven't installed it not suffer it, I think it is likely due to something within the hotfix update. But since the limitation of the troubleshooting assistance we can do, I suggest that you request a regular case from the MS PSS (which can do some thorough troubleshootings such as dump analysis) if you feel this an urgent issue. Also, if there is anything else we can help, please feel free to post here. Thanks. Regards, Steven Cheng Microsoft Online Support OK Steven will do. As always, thanks for your help! Stu > Hi Stu, > [quoted text clipped - 16 lines] > Steven Cheng > Microsoft Online Support Hi Stu, Thanks for the followup and hope the problem soon be resolved. Also, please always feel free to post here if you have any other questions next time. Thanks again for posting. Regards, Steven Cheng Microsoft Online Support SignatureGet Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.) This line in Machine.config after the 5th occurance of "processmodel": <compilation debug="false" explicit="true" defaultLanguage="vb" batchTimeout="30" maxBatchGeneratedFileSize="10000"> Will help complex projects not have problems building sporadically as I've been having for quite some time now. The defaults have much smaller sizes. HTH >-----Original Message----- >Hi Steven [quoted text clipped - 44 lines] > >. I run the same environment described above and am experiencing the same issue. > Hi, > [quoted text clipped - 28 lines] > Thanks, > Stuart I've been experiencing the same problems. Using VS.Net 2003/Framework 1.1 on a IBM ThinkCentre - Pentium 4 - 2.8Ghz - 512MB DDR 3300 Ram Developing ASP.Net website in a large solution containing 4 projects. This is my 3rd installation of Win XP and VS.Net 2003 and still experinecing the same memory problem. Initially when I open my solution I can see in the task manager, that devenv.exe is using around 55MB of memory and 55MB of VM. When I start rebuilding the solution it takes 70MB mem and VM. If I start the application it takes 90MB mem and VM. Now as I stop the application I would assume that VS.Net would go back to using 55MB but this does not seem to be the case, it still uses 90MB. If I start the application again and also want to debug the code, VS.Net now takes 290MB of mem and 380MB of VM, and when I stop debugging it still uses the same amount of memory. Next time I start the application and want to debug, it starts at 290MB mem and 390MB VM and rises to 400MB mem and 700MB VM. For each time I debug my application it takes another 100-200MB. In the end it used all avaliable memory and 1,5GB of VM THAT IS NOT GOOD. Because of this I need to shut down VS.Net 10 times a day which is very time consuming. HELP - Please - anyone ;o) Not sure if it is related, but I haven't had the problem since I coped some local assemblies into the GAC... Sometimes after a build, I would launch the web app and be presented with an ASP.Net debug page claiming that a compilation error had occurred - "MetaData file xxx.dll could not be found". The dll was there though. I put the DLL into the GAC but still referenced it locally and I've not seen either problem since. HTH! > I've been experiencing the same problems. > Using VS.Net 2003/Framework 1.1 on a IBM ThinkCentre - Pentium 4 - 2.8Ghz - [quoted text clipped - 30 lines] > > HELP - Please - anyone ;o) Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.