Comments
Sort by recent activity
Thanks for the update regarding updates. [image]
So far, 1088 seems more stable than 1039, at least for me profiling a Winforms app targetting .NET 2.0. Had a couple of crashes with 1039 but none yet so far on 1088.
Likes:
File I/O events.
My main dev machine is using XP, but I have managed to try 1088 out in a Win 7 machine to take a look at this feature, and I do like this very much. Works well, and is certainly an eye-opener (for me) to see the activity that is going on.
'Method events'
Good stuff. I like the ability to click on the 'method event' bar and have the selected portion of the timeline fit to the method.
Dislikes:
None really, but I do have a couple of minor comments.
1. I preferred the tab where you can select which performance counters to add to the timeline when profiling to be labelled 'Performance Counters' instead of 'Charting Options'.
2. As my dev machine is running XP, the option to enable file I/O and SQL events is disabled, correctly, as you say can only profile these in Vista and above. However, when the 'hints' feature detects, for example, a section with high file I/O, it still pops up and says I can switch analysis modes to show the file I/O activity, when of course I cannot.
Only a couple of minor points, but there you go - my 2p.
Not tried sampling mode yet, but I will do so.
All in all, thumbs up. / comments
Thanks for the update regarding updates.
So far, 1088 seems more stable than 1039, at least for me profiling a Winforms app targetting .NET 2.0. Had a couple of crashes with 1039 but none yet so f...
Managed to install V5.2 on a Win7 32 bit machine and tried it. Not unexpectedly based on your results, it works fine.
So, it looks very much like the problem lies on my main dev machine.
Would you still be willing to look at a crash dump if it is possible to generate one?
(Obviously the problem looks to be at my end rather than with Red Gate, so I understand if you can't.) / comments
Managed to install V5.2 on a Win7 32 bit machine and tried it. Not unexpectedly based on your results, it works fine.
So, it looks very much like the problem lies on my main dev machine.
Would you ...
Somehow, I just knew you would say that. I can't decide if that is good or bad news!
My machine is kept fully updated, but maybe a corrupted install of something is causing trouble?
Possibly a reinstall of the frameworks could be in order?
Either way, I guess Red Gate is in the clear...
I will endeavour to try it on another machine and see if I can't isolate where the problem is.
Ah well, the least you can do is Reflector around my code and point & laugh. [image]
Thank you for trying it out. / comments
Somehow, I just knew you would say that. I can't decide if that is good or bad news!
My machine is kept fully updated, but maybe a corrupted install of something is causing trouble?
Possibly a rein...
Yep, thanks. I have actually emailed support to that effect already. / comments
Yep, thanks. I have actually emailed support to that effect already.
Hi Andrew, thank you for your reply.
My app does use sockets directly, as well as using the serial port for communications with some PLC controlled OEM equipment. It does not connect to any remote database.
However, none of the socket creation or connect code is hit when the app starts, at least not by default. I have another app I use to simulate the PLC equipment using sockets to help me debug my main app, and this gets profiled without problem.
The app has contained socket code since I first purchased the profiler, and as I say, it used to work. Indeed, I used to to profile the socket code at the time.
Not sure if this is relevant or not, but the app can be used with the memory profiler without issue.
I am using a 3rd party library from ICSharp. (ICSharpCode.SharpZipLib.dll V0.85.5.452)
Other tests that cause a crash:
Setting the profiler to use the fastest profile method.
Profiling both Debug and Release builds.
At this point, the app crashes 100% of the time, right at the start. (I have a gimmicky splash screen that is the first thing to run, and this does not get the chance to appear before the crash dialog is displayed. I also disabled this, in case my gimmicks were causing grief.)
I'll do some more tests, and see if I can perform any hacks that allow it to run. I will be sure to disable anti-virus and firewall as well to see if it helps. In the event of any success, I will be sure to let you know.
In the meantime, if there is any more info you would like, let me know, thanks. / comments
Hi Andrew, thank you for your reply.
My app does use sockets directly, as well as using the serial port for communications with some PLC controlled OEM equipment. It does not connect to any remote ...
Well, I've hacked around, disabled anti-virus, disabled firewall, checked and unchecked all of the profiler options and it still crashes.
I have even disabled running of the main form so the app is basically doing nothing at all: Still crashes.
I have also tried the V6 EAP and it crashes with this also. It does do something slightly different though - I still get the crash dialog appear, but the app itself does load and run. The profiler however is not doing anything, and as soon as I clear the crash dialog, the app closes and the profiler reports no results.
Both V5 and V6 EAP profilers correctly work on other apps, it is just this one that fails. Unfortunately, that is the one I want to profile.
I am at a loss on what to do next. Can I send you the .exe perhaps? Would that be of use?
Please help! / comments
Well, I've hacked around, disabled anti-virus, disabled firewall, checked and unchecked all of the profiler options and it still crashes.
I have even disabled running of the main form so the app is...
Thanks for the reply...
Chocolate teapot eh? I'm inclined to agree.
No events regarding .NET or ANTS in the Windows event logs, merely the app error event which echoes the info I posted above.
I have no problem generating a 'mini'dump' for you. How do I go about that?
Let me know and I'll give it a try, thanks. / comments
Thanks for the reply...
Chocolate teapot eh? I'm inclined to agree.
No events regarding .NET or ANTS in the Windows event logs, merely the app error event which echoes the info I posted above.
I ha...