Host.Local.FindSingle hangs if search process in dead lock
Posted: Tue Jul 12, 2016 10:19 am
Hello,
I have a test where I exit our application. Unfortunaly due to a failure in our KDE implementation the process don't exit but remain in a dead lock issue, so the process is still existing.
My problem is that the Host.Local.FindSingle method never throw an exception if the duration time is expired.
In the test I start the application after calling "Exit" again and try to click at a menu, using the Host.Local.FindSingle method to get the menubar. This call never come back until I kill the dead locked process.
In the attached screenshot you see at the left side the debug message I write before calling the Host.Local.FindSingle with 2000 ms duration (time stamp 10:56:03,970)
At the right bottom corner the clock is at 11:01.
Above you see the two processes, the grey is the dead one, and his thread 6252 and the stack of the thread.
I have a test where I exit our application. Unfortunaly due to a failure in our KDE implementation the process don't exit but remain in a dead lock issue, so the process is still existing.
My problem is that the Host.Local.FindSingle method never throw an exception if the duration time is expired.
In the test I start the application after calling "Exit" again and try to click at a menu, using the Host.Local.FindSingle method to get the menubar. This call never come back until I kill the dead locked process.
In the attached screenshot you see at the left side the debug message I write before calling the Host.Local.FindSingle with 2000 ms duration (time stamp 10:56:03,970)
At the right bottom corner the clock is at 11:01.
Above you see the two processes, the grey is the dead one, and his thread 6252 and the stack of the thread.