Window messages

From: Berndt Johansson (berndt.johansson_at_removenospamom.com)
Date: 06/28/04 

Date: Mon, 28 Jun 2004 20:09:19 +0200

Hi

I just stumbled into a strange problem that I don't understand. My launcher
application starts an executable after the load event. Actually I have the
Load event handler set a timer for 200ms and the timer's Tick handler will
do some work and then eventually start the application using Process.Start.
In the execution of the Timer event I use a Process.WaitForExit function to
halt the execution until the started application exits. This usually works
fine, but not always. Our fault reporting system stopped working when people
started using the launcher application and the reason for this seems to be
that the timer's event handler will not finish until the launched
application is closed.

For some reason it seems to me that the Remedy system stopped to receive
window messages when my launcher application was running the timer event.
When that timer event was finished executing (the launched application was
closed) the Remedy application would just continue to work as nothing had
happened.

Why is this not happening for all applications?

My workaround was to use a separate thread that would launch the executable.
I was still able to use the WaitForExit and when the tread was finished, the
launcher would also exit.

But the behaviour really puzzles me!

Can anyone please shed some light on this?

/Berndt

Relevant Pages

  • [patch 15/21] clockevents: drivers for i386
    ... lapic and PIT. ... Update the timer IRQ to call into the PIT driver's event handler ... * of the boot CPU and register the clock event in the framework. ...
    (Linux-Kernel)
  • [patch 15/22] clockevents: drivers for i386
    ... lapic and PIT. ... timer IRQ to call into the PIT driver's event handler and the lapic-timer IRQ ... * of the boot CPU and register the clock event in the framework. ...
    (Linux-Kernel)
  • Re: Help with design
    ... If so, put a timer in Session, ... and set up an event handler for the timer's Elapsed event that does what you ... If it is for all users, put the timer in Application Cache. ... Now you want to know how to modify that Control to do what you ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Debugging Challenge - no source available
    ... > custom controls. ... > few bitmap operations which use a timer to help time-slice so the UI ... > - the debugger stops at the Application.Runline, there's no call stack, ... > In both cases, the debugger catches execution at the same point, just ...
    (microsoft.public.dotnet.general)
  • Re: System.Timers.Timer and Close/Dispose
    ... They could have dealt with a race condition just by setting a volatile boolean variable that signals to the timer event handler that the timer's been stopped and so shouldn't do any work. ... the handler could still already be executing past the point at which is actually attempts to check the status variable they're using. ... it's still possible to have timer handler code execute after disabling the timer. ...
    (microsoft.public.dotnet.framework)
Loading