Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-09-28 Thread Fabian Schmied
.SystemEvents.OnUserPreferenceChanged event. Mike seems to have found the reason for that problem, so I'm forwarding his mail to this list, see below. Fabian -- Forwarded message -- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Sep 28, 2006 5:06 PM Subject: Re: [ADVANCED-DOTNET] Odd stack

Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-05-22 Thread Dmitry Shaporenkov
ipped into .NET 2.0 somehow... > -Original Message- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Fabian Schmied > Sent: Monday, May 22, 2006 4:40 PM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] O

Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-05-22 Thread Fabian Schmied
Following up on this old thread: [UserPreferenceChanged deadlock with stacktrace showing blocked thread at WaitForMultipleObjects via Control.Invoke via OnUserPreferenceChanged] I found a KB article which describes the problem the OP was having, saying it is caused by a bug in DateTimePicker, Mo

Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-02-25 Thread Dmitry Shaporenkov
ary 24, 2006 2:10 PM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app > > > The problem is almost 100% reproducible, and during the > last debugging > > session I noticed only two managed threads: > > the f

Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-02-24 Thread Fabian Schmied
> The problem is almost 100% reproducible, and during the last debugging > session I noticed only two managed threads: > the first one is the primary thread with the stack trace I posted in the > original message, and the second one is a background > worker thread which performs jobs in the backgro

Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-02-23 Thread Dmitry Shaporenkov
gt; Subject: Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app > > > Could you please clarify what makes you think that the target UI > > thread differs from the original thread? > > I took a look at Control.MarshaledInvoke in Reflector (code is below). > > First,

Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-02-23 Thread Fabian Schmied
> Could you please clarify what makes you think that the target UI thread > differs from the original thread? I took a look at Control.MarshaledInvoke in Reflector (code is below). First, MarshaledInvoke creates an "entry1" variable holding the event handler method and marshals it (i.e. enqueues

Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-02-23 Thread Dmitry Shaporenkov
of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Fabian Schmied > Sent: Thursday, February 23, 2006 12:01 PM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app > > > I'm facing odd hang-up

Re: [ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-02-23 Thread Fabian Schmied
> I'm facing odd hang-ups in a mixed unmanaged/Win Form app (actually this is > a VS 2005 with a managed add-in loaded) > that I think might be of interest here. The stack trace of the UI thread > (captured using WinDbg) is posted below. Basically, > what is happening here is some system event > (M

[ADVANCED-DOTNET] Odd stack trace from a hung .NET app

2006-02-21 Thread Dmitry Shaporenkov
Hi there, I'm facing odd hang-ups in a mixed unmanaged/Win Form app (actually this is a VS 2005 with a managed add-in loaded) that I think might be of interest here. The stack trace of the UI thread (captured using WinDbg) is posted below. Basically, what is happening here is some system event (