User profile for stevehurcombe

Hi, Actually it turned out to be a bit simpler than that. I had these problems: First I had to disable MS AntiSpyware (will you be fixing this in the future). Then I discovered that I couldn't use the syntax http://localhost/default.aspx (ie it has to be a folder). Come on, this shouldn't cause an exception! Finally I discovered that there was a profiler process hanging around (probably a dead one from all the exceptions) once I killed that it seemed to run OK. On the whole it seems to do the job - bit it's a bit 'fragile' to say the least... S. / comments

Hi, Actually it turned out to be a bit simpler than that. I had these problems: First I had to disable MS AntiSpyware (will you be fixing this in the future). Then I discovered that I couldn't use ...

0 votes

H, I think is was Redgate.Profiler.UI.exe or something... S. / comments

H, I think is was Redgate.Profiler.UI.exe or something... S.

0 votes

Hi, One small point the browser starts and I get a 404 error. Hitting refresh though starts things up nicely. S. AndrewH wrote: There's a bug somewhere in the UI logic that leaves the 'summarizing' screen up when the target process has stopped before .NET has started. It's supposed to display a message to the effect that there are no results available instead (which is still kind of unhelpful, but unfortunately it's all that the profiler can really see happening). With an ASP.NET application, ANTS monitors an instance of Internet Explorer, and stops profiling once it goes away. Sometimes IE farms off the request from ANTS to another instance of itself and quits immediately, which looks to ANTS the same as if you had closed the window. I think from your description that this is most likely what's happening (if this is what's happening, then the 'summarizing results' spinny will show up around the same time the browser opens). If the 'stop profiling' button is grayed out when the browser is open, then this is almost certainly what's happened: it's only lit while the profiler thinks that the target process is running. One thing to look for is whether or not protected mode is on when the browser opens. ANTS *should* be creating a browser that is running with protected mode turned off. If protected mode is on, then one thing that might fix the issue is manually turning it off in IE's settings. Which version of IE are you running? IE7 has protected mode but doesn't have a way to start with it turned off (the feature was added in IE8), and might be a source of these issues. Something else that might be worth trying is profiling the C:\Program Files\Internet Explorer\iexplore.exe process using the desktop application profiling mode. The profiler shouldn't display the spinner until after IE exits: if it shows up right away then there's something odd going on (the spinner won't disappear due to the UI bug, at least, unless you load a page with Silverlight on it). / comments

Hi, One small point the browser starts and I get a 404 error. Hitting refresh though starts things up nicely. S. AndrewH wrote: There's a bug somewhere in the UI logic that leaves the 'summarizing...

0 votes

Hi, That fixed it. I am running IE9 and it had launched in protected mode. Disabling that fixed the problem. Thanks! S. AndrewH wrote: There's a bug somewhere in the UI logic that leaves the 'summarizing' screen up when the target process has stopped before .NET has started. It's supposed to display a message to the effect that there are no results available instead (which is still kind of unhelpful, but unfortunately it's all that the profiler can really see happening). With an ASP.NET application, ANTS monitors an instance of Internet Explorer, and stops profiling once it goes away. Sometimes IE farms off the request from ANTS to another instance of itself and quits immediately, which looks to ANTS the same as if you had closed the window. I think from your description that this is most likely what's happening (if this is what's happening, then the 'summarizing results' spinny will show up around the same time the browser opens). If the 'stop profiling' button is grayed out when the browser is open, then this is almost certainly what's happened: it's only lit while the profiler thinks that the target process is running. One thing to look for is whether or not protected mode is on when the browser opens. ANTS *should* be creating a browser that is running with protected mode turned off. If protected mode is on, then one thing that might fix the issue is manually turning it off in IE's settings. Which version of IE are you running? IE7 has protected mode but doesn't have a way to start with it turned off (the feature was added in IE8), and might be a source of these issues. Something else that might be worth trying is profiling the C:\Program Files\Internet Explorer\iexplore.exe process using the desktop application profiling mode. The profiler shouldn't display the spinner until after IE exits: if it shows up right away then there's something odd going on (the spinner won't disappear due to the UI bug, at least, unless you load a page with Silverlight on it). / comments

Hi, That fixed it. I am running IE9 and it had launched in protected mode. Disabling that fixed the problem. Thanks! S. AndrewH wrote: There's a bug somewhere in the UI logic that leaves the 'summ...

0 votes

It seems that the VS 2010 profiler won't work either. This page suggests that there is a location element missing (I'm getting an identical error): http://netindonesia.net/blogs/jimmy/arc ... t-not.aspx Could that be tripping up ANTS too? S. Brian Donahue wrote: Yes, but need to reproduce in-house. This softeware is totally unfriendly to production debugging. Obviously ANTS Profiler is causing your program to crash, that's problem number one. Then there is a deadlock bug on summaraizing - that's problem number two. So I need to have this happen on my computer. What special thing is ProfilerCore.dll doing that hoses your application in the first place? Is there anything in the event log? / comments

It seems that the VS 2010 profiler won't work either. This page suggests that there is a location element missing (I'm getting an identical error):http://netindonesia.net/blogs/jimmy/arc ... t-not....

0 votes

Hi Brian, Scratch that. VS 2010 started working I just ran it again...doh! S. Brian Donahue wrote: Yes, but need to reproduce in-house. This softeware is totally unfriendly to production debugging. Obviously ANTS Profiler is causing your program to crash, that's problem number one. Then there is a deadlock bug on summaraizing - that's problem number two. So I need to have this happen on my computer. What special thing is ProfilerCore.dll doing that hoses your application in the first place? Is there anything in the event log? / comments

Hi Brian, Scratch that. VS 2010 started working I just ran it again...doh! S. Brian Donahue wrote: Yes, but need to reproduce in-house. This softeware is totally unfriendly to production debugging...

0 votes

Hi Brian, Completely understand, obviously I can reproduce it here - happy to have a remote desktop session if that helps. It happens 100%. Cheers Steve Brian Donahue wrote: Looks like we're in another one of those "unless you can reproduce it we won't try to fix it" arguments. At one point, I could get this to happen sometimes by killing the process being profiled in Task Manager. But I can't get it to happen reliably enough. Any pointers as to how I can hang Profiler on summarizing results are most welcome. / comments

Hi Brian, Completely understand, obviously I can reproduce it here - happy to have a remote desktop session if that helps. It happens 100%. Cheers Steve Brian Donahue wrote: Looks like we're in an...

0 votes

These are the steps: 1. Start a profile session. 2. The browser loads but displays a 404 message. 3. ANTS spins 'Summarizing results'. 4. If I refresh the browser page then the API call works and a new W3P process is NOT created. There are no messages in the event log other than 'Message logging has been turned on'. The W3P process that reported the message is still active and hasn't crashed. If my code had really died I would have expected that process to die as well?? If I attach to the process directly then all is well. I can also profile an ASP.Net 3.5 (2.0) application just fine on the same machine. The only unusual factor that I can think of is that this is a WCF 4.0 application. There's nothing complicated about the application itself. I wonder if the profile is starting too quickly? After IIS is listening but before WCF has started. Is there any additional logging I can enable? Best regards Steve Brian Donahue wrote: Yes, but need to reproduce in-house. This softeware is totally unfriendly to production debugging. Obviously ANTS Profiler is causinf you rprogram to crash, that's problem number one. Then it was a deadlock bug on summaraizing - that's problem number two. So I need to have this happen on my computer. What special thing is ProfilerCore.dll doing that hoses your application in the first place? Is there anything in the event log? / comments

These are the steps: 1. Start a profile session. 2. The browser loads but displays a 404 message. 3. ANTS spins 'Summarizing results'. 4. If I refresh the browser page then the API call works and a...

0 votes

Hi Brian, I'm getting the same symptoms as this with a WCF 4 application in IIS. I can attach to the process OK and run a profile, but it's not a line level analysis. Do you have an update? Many thanks Steve Brian Donahue wrote: Thanks for posting in the Performance Profiler forum. I think there are two issues at work. One is that IE doesn't give us a predictable process ID for the instance of iexplore.exe running the Silverlight. The only way to make it work reliably is to kill all instances of IE from Task Manager (some may not even be "visible"). The second problem is a bug that when there are no results or an error occurs sending results, the green thing spins around forever ( PP-1144 ). We're working to get this fixed. / comments

Hi Brian, I'm getting the same symptoms as this with a WCF 4 application in IIS. I can attach to the process OK and run a profile, but it's not a line level analysis. Do you have an update? Many th...

0 votes

Daniel Handley wrote: Hi Steve The most likely cause of the addition of a deselected object is that you have "include dependencies" selected. This means that any deselected objects that have dependencies to a selected object will still be included. Regards Dan Possibly, it was certainly ticked, I will have to look that up. It would be nice if the 'included' dependancy was highlighted a little better - the change would have broken our system if I hadn't removed it. Many thanks Steve / comments

Daniel Handley wrote: Hi Steve The most likely cause of the addition of a deselected object is that you have "include dependencies" selected. This means that any deselected objects that have dep...

0 votes

How can we help you today?

stevehurcombe

Comments