Comments
Sort by recent activity
We now have two workarounds for crashes:
1. What we have found that works is disabling the server garbage collector as described here: <http://support.microsoft.com/kb/911716>
Remember- "server GC" actually means multi-core GC.
2. Parametize your main method with:
[System.LoaderOptimization(LoaderOptimization.MultiDomain)]
or
[System.LoaderOptimization(LoaderOptimization.MultiDomainHost)]
If you don't have a main method, for example: if you have a WPF project, take a look at this article which shows you how to do it: http://www.matthidinger.com/archive/200 ... ation.aspx / comments
We now have two workarounds for crashes:
1. What we have found that works is disabling the server garbage collector as described here: <http://support.microsoft.com/kb/911716>
Remember- "server ...
and my analysis is sometimes even better than my spelling. [image] / comments
and my analysis is sometimes even better than my spelling.
If you send results to: support@red-gate.com I'm alwayd happy to discuss them. / comments
If you send results to: support@red-gate.com I'm alwayd happy to discuss them.
I think its because vbscript.dll is not registered by default on some machines (security reasons I think). There is plenty of info in googlespace on this. e.g.: http://social.msdn.microsoft.com/Forums ... c5f63086b8 / comments
I think its because vbscript.dll is not registered by default on some machines (security reasons I think). There is plenty of info in googlespace on this. e.g.:http://social.msdn.microsoft.com/Foru...
Yes, 1603 is actually a generic error (5.1 only solves one issue but it was occuring very frequently). Can you get hold of the install log file. Click on the very top left corner of the installer and the menu will give you acces to the log file. If there are grumblings about VBScript, try this:
Running CMD.exe as Administrator:
cd %windir%\System32
regsvr32 vbscript.dll
or this, on x64:
cd to C:\windows\syswow64
Type- regsvr32 vbscript.dll, then hit enter. / comments
Yes, 1603 is actually a generic error (5.1 only solves one issue but it was occuring very frequently). Can you get hold of the install log file. Click on the very top left corner of the installer a...
We will release version 5.1 on Tuesday 14th July. This will fix the current installation problems. Sorry for the delay. / comments
We will release version 5.1 on Tuesday 14th July. This will fix the current installation problems. Sorry for the delay.
Sorry that you're still having troubles, I'll post as soon as I know... / comments
Sorry that you're still having troubles, I'll post as soon as I know...
On behalf of the Developer team here- thank you. / comments
On behalf of the Developer team here- thank you.
Hi jasonglovernz, thanks for the post. I think what you proposed sounds like an good use-case for ANTS profiler. 100 users sounds about right- possibly a little on the high side but "who dares, wins" I believe in web site testing. :-)
At Red-Gate we haven't done anything systematically in this respect as we haven't tended to see it as a live testing tool but I'd be happy for us to go in this direction - especially with our Memory profiler (as it has the least overhead of any of the competition by far).
So, in summary: go for it but please throttle the users until is proved to be a good model. / comments
Hi jasonglovernz, thanks for the post. I think what you proposed sounds like an good use-case for ANTS profiler. 100 users sounds about right- possibly a little on the high side but "who dares, win...
Hi there. I've got your support call now and I've been reading through the history. So- to start with, no, hopefully you didn't buy ANTS for nothing [image] We do get a number of crashes-under-profiling and they happen for a variety of reasons, most of which we solve and some of which we cannot. I'll endeavour to find out which one we have here but this will need a fair bit of debugging.
Firstly, please would you set the logging to full debug mode i.e. in the file
%userprofile%\Local Settings\Application Data\Red Gate\ANTS Performance Profiler 5\LoggingConfiguration.xml
change all the "tagged blocks" to look like the following:
<root>
<level value="DEBUG" />
<appender-ref ref="DefaultRGFile" />
</root>
<logger name="RedGate.Profiler.Engine">
<level value="DEBUG"/>
</logger>
<logger name="RedGate.Profiler.Logging">
<level value="DEBUG" />
</logger>
<logger name="RedGate.Profiler.Monitoring.PerformanceCounterFactory">
<leval value="DEBUG"/>
</logger>
(wierdly enough, you'll need to change instances of "leval" to "level" as well - sorry!)
Then please reproduce the problem and send us the resulting logfile (to support@red-gate.com).
We then may need to force and look at a dump of the crash (this is what we mean by a mini-dump- "mini" signifying that it is from the .NET runtime, I believe). We usually use windbg and I can drive this from a shared web session if you like.
But first, I think the debug logs would be a good start.
Cheers. / comments
Hi there. I've got your support call now and I've been reading through the history. So- to start with, no, hopefully you didn't buy ANTS for nothing We do get a number of crashes-under-profiling a...