Activity overview
Latest activity by DanNeilsen
ok, I found a bug that had been introduced into my code and, when I correct it the profiler started to work again.
Not sure why this affected the profiler but this is basically what was occuring.... private void mainForm_Load(object sender, EventArgs e)
{
.....
//Start online thread that checks online state
_OnlineState = new DLA.core.http.OnlineStateThread();
_OnlineState.onStateChange += new DLA.core.http.OnlineStateChangeHandler(_OnlineState_onStateChange);
_OnlineState.StartTest();
//This is was the problem line
mainForm_Load_B();
}
private void _OnlineState_onStateChange(DLA.core.http.OnlineStateValue CurrentState)
{
OnlineState = CurrentState;
if(initState == 0)
mainForm_Load_B();
}
private void mainForm_Load_B()
{
//Continue program load here
}
Now quite obviouslly, this was doubly initialising my program.
Not sure why this caused the profiler to die but... hopefully this info helps you track the issue down [image] / comments
ok, I found a bug that had been introduced into my code and, when I correct it the profiler started to work again.
Not sure why this affected the profiler but this is basically what was occuring......
Just a little more info.
If I click the "Disable Profiler" button and then click "Start Profiling" the application will run fine. / comments
Just a little more info.
If I click the "Disable Profiler" button and then click "Start Profiling" the application will run fine.
I am also having the same problem.
I have been using the profiler successfully on this application for several weeks.
I am using the profiler on a debug version C# .Net desktop app and, when run, it starts the application and runs partially through the applications initialisation process and then just freezes, sitting on 100% cpu.
Attempting a snapshot does not work but pressing the "Stop Profiling" button will shut the application down cleanly as per normal.
The other thing that is odd is that it does not always stop at exactly the same line of code. It will generally stop in the same area, almost as if the problem is time based.
For the record, the application runs fine when not profiling.
Note sure if this will help at all but I am running winxp with sp2, on a P4 3ghz HT cpu with 1gb of ram. / comments
I am also having the same problem.
I have been using the profiler successfully on this application for several weeks.
I am using the profiler on a debug version C# .Net desktop app and, when run, i...