Comments
Sort by recent activity
Hi Paul,
Thanks for getting in touch. ANTS Profiler will only provide click navigation in the source code view for methods that were executed. This is because to provide click navigation for all methods would require a complete model of the code being executed, which we don't construct since it would impede performance and increase the profiler overhead.
I suspect therefore, the reason that you're not seeing a hyperlink for the no-args constructor is that it wasn't executed in the NewQuestions method. As for why it's taking you to line 13, I suspect this is because this probably was the first line of code that was executed during that constructor call. Static variables are initialised the first time a class is used, so I'm assuming this is what happened here. Similarly, member variables that are initialised outside of a constructor are also collapsed into the constructor call for execution purposes (note the way the VS debugger steps through these initialisations before stepping into a constructor body).
Obviously this isn't made entirely clear, however it's difficult to determine what the correct behaviour should be since a class or instance level initialisation outside of a constructor could be very expensive. Also, I suspect the lack of a complete code model may possibly limit what we can do here.
At any rate I'll add this to the list of things we can look into improving. Hope that's useful information.
Thanks,
Bart / comments
Hi Paul,
Thanks for getting in touch. ANTS Profiler will only provide click navigation in the source code view for methods that were executed. This is because to provide click navigation for all me...
Hi Chris,
There's a new build now available that should work for you: http://www.red-gate.com/messageboard/vi ... php?t=7695
Again, apologies for the difficulties you've had.
Thanks,
Bart / comments
Hi Chris,
There's a new build now available that should work for you:http://www.red-gate.com/messageboard/vi ... php?t=7695
Again, apologies for the difficulties you've had.
Thanks,
Bart
Hi Chris,
Sorry about this! What a royal pain in the backside. We should have something sorted for you today, all being well.
Thanks,
Bart / comments
Hi Chris,
Sorry about this! What a royal pain in the backside. We should have something sorted for you today, all being well.
Thanks,
Bart
Hi Chris,
I've just posted up a build with a fix for this issue. Please refer to the early access build announcement in the main forum for download details: http://www.red-gate.com/MessageBoard/viewforum.php?f=86
If there's anything else please let me know.
Thanks,
Bart / comments
Hi Chris,
I've just posted up a build with a fix for this issue. Please refer to the early access build announcement in the main forum for download details:http://www.red-gate.com/MessageBoard/view...
Hi Chris,
OK, sorry about this, it looks like the installer didn't register the new DLL properly.
This might do the trick (I'm assuming you're running 32-bit Windows XP).
Open up a command prompt. Navigate to the ANTS Profiler installation directory, which is probably something like "C:\Program Files\Red Gate\ANTS Profiler 4" using the following:
cd "C:\Program Files\Red Gate\ANTS Profiler 4"
Now, execute the following command:
regsvr32 ProfilerCore.dll
That should register the correct version of the ProfilerCore DLL. You should then be able to run ANTS Profiler.
If you're running 64-bit Windows , it's slightly more involved. Open up a 64-bit command prompt, and as before change to the ANTS Profiler installation directory. You need to register both the 32- and 64-bit profiler cores, so once you're in the right directory first register the 32-bit DLL using:
C:\Windows\SysWOW64\regsvr32.exe ProfilerCore.dll
Now cd into the x64 subdirectory and register the 64-bit DLL using:
regsvr32 ProfilerCore.dll
If that doesn't work then
(i) Completely uninstall ANTS Profiler 4.1 using "Add/Remove Programs" in Control Panel (I think it's is called "Programs and Features" on Vista).
(ii) Re-install ANTS Profiler 4.1 using the installer you downloaded earlier for build 4.1.0.11.
If you're still not getting any joy please let me know and I'll look into it further.
Thanks,
Bart / comments
Hi Chris,
OK, sorry about this, it looks like the installer didn't register the new DLL properly.
This might do the trick (I'm assuming you're running 32-bit Windows XP).
Open up a command prompt. ...
Hi Chris,
Sorry to see you're having problems.
I've spent some time today looking at this problem, and I've managed to apply a fix that should sort it out for you. The downside is that we're just now migrating version control systems so I won't be able to get you a patch until the new version control system is integrated with our build service. We'll also need to check the upgrade routes all work in the installer.
Things are a little chaotic at the moment because a number of key people involved in the project are taking chunks of well earned holiday, including me in a couple of weeks, however we'll try to get something sorted out for you as quickly as we can. Don't worry about your trial period expiring; we can sort that out as well.
Just in case it's helpful, as far as I can tell the issue can be caused by one of the following scenarios:
- High CPU load causing a COM+ server to take an excessively long time to start up.
- Having a debugger attached to the COM+ server, with execution paused
- A bug in a COM+ server that prevents it registering itself properly.
- Incorrect registration/configuration of a COM+ server.
- Some other reason (yeah, I know, it's lame) that isn't listed above--I'm no COM+ expert.
I'm assuming you're probably not trying to profile a COM+ server, so this'll be just something that's installed on your machine by another application, so it may not be something you're in a position to do anything about. At any rate, failures such as these are things we're going to have to deal with, although unfortunately until something like this happens you've often no idea that this kind of thing could cause a problem, given the vast number of other scenarios we have to test.
I'll let you know when the patch becomes available.
Thanks,
Bart / comments
Hi Chris,
Sorry to see you're having problems.
I've spent some time today looking at this problem, and I've managed to apply a fix that should sort it out for you. The downside is that we're just n...
Hi Chris,
Not any more unfortunately, although we've had a conflab and are now hoping to get a 4.1 early access build out on Monday or Tuesday next week with this fix in.
I'll keep you posted.
Thanks,
Bart / comments
Hi Chris,
Not any more unfortunately, although we've had a conflab and are now hoping to get a 4.1 early access build out on Monday or Tuesday next week with this fix in.
I'll keep you posted.
Than...
OK, thanks Scott. It was a bit of a long shot. / comments
OK, thanks Scott. It was a bit of a long shot.
Thanks Scott,
Another couple of questions:
1) What happens if you uncheck "Profile child processes" in the "Performance Profiler Settings" dialog and then profile your app?
2) Could you send us the ProfilerCore.dll that's registered with your system please? Please note: this may not be the ProfilerCore.dll under the ANTS Profiler 4 directory. To find it open up regedit.exe and navigate to "HKEY_CLASSES_ROOT\CLSID\{A07CBDF0-B23B-4A96-A889-18E3C3004EB2}\InprocServer32". The filename is the data for the "(Default)" value under this key. Once you've got this can you send the file to bartDOTreadATredHYPHENgateDOTcom.
Thanks,
Bart / comments
Thanks Scott,
Another couple of questions:
1) What happens if you uncheck "Profile child processes" in the "Performance Profiler Settings" dialog and then profile your app?
2) Could you send us the...