SplashScreen throws exception - by StefanOlson

Status : 

 


19
0
Sign in
to vote
ID 362735 Comments
Status Active Workarounds
Type Bug Repros 23
Opened 8/20/2008 7:31:42 PM
Access Restriction Public

Description

In my app, using SplashScreen, I will sometimes get this exception:
System.ComponentModel.Win32Exception: The operation completed successfully
Here's the call stack:
   at MS.Win32.UnsafeNativeMethods.SetActiveWindow(HandleRef hWnd)
   at System.Windows.SplashScreen.Close(TimeSpan fadeoutDuration)
   at System.Windows.SplashScreen.<Show>b__0(Object splashObj)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
   at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at System.Windows.Application.Run(Window window)
   at System.Windows.Application.Run()
   at VirtualTourViewer.App.Main() in C:\projectswpf\VirtualTourViewer\VirtualTourViewer\obj\x86\Debug\App.g.cs:line 0
   at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
   at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
   at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Sign in to post a comment.
Posted by Maximilian Haru Raditya on 11/8/2009 at 12:08 PM
I agree with previous posters. A hotfix for .NET 3.5 SP1 is urgently needed. I thought this was initially reported for it, but somehow it's only fix in .NET 4.0.

Thanks!
Posted by DavidADugan on 8/11/2009 at 2:41 PM
To echo Rick (Rytis Ilciukas) here, I'd also like a hotfix for this issue. Saying it will be fixed in the next release is all fine and dandy except that A) .Net 4.0 isn't out yet, and B) My clients are unlikely to switch to it immediately anyways.

If there already IS a hotfix, my apologies, I couldn't find it!
Posted by Rytis Ilciukas [Rick] on 5/4/2009 at 12:49 AM
How about a hotfix? Please MS guys :)
Posted by Microsoft on 4/16/2009 at 5:30 PM
Thanks to everyone who reported this issue. The bug has been fixed in the next release of WPF, .NET 4.0.

Thank you!
Windows Presentation Foundation Product Team
Posted by Artur H. Shamsutdinov on 3/31/2009 at 1:15 AM
Sorry, I mean we are experiencing the same problem in our WPF application.
Posted by Artur H. Shamsutdinov on 3/31/2009 at 1:14 AM
We expecting the same problem in our WPF application.
Posted by gboulbes on 1/16/2009 at 5:45 AM
Hi,
My team and I do have exactly the same issue at this moment and didn´t succed to fix it.
Did you find a workaround for this bug or any explanations?
That will be really helpfull for us if we solve it!
Thanks a lot in advance for your responses!
Regards,
Guillaume
Posted by Auzani Ridzwan on 12/15/2008 at 8:26 PM
Actually we have found out that the problem is reproducible. When the app starts click on another window (making it not the active app). When your app is ready the exception will be thrown. Looking at the stack trace:

at MS.Win32.UnsafeNativeMethods.SetActiveWindow(HandleRef hWnd)

it seems there is a problem with this method if the current app is not the active window.

It happens frequently in debug mode obviously because VS becomes the active window when u hit a breakpoint thus reaching the above condition.
Posted by Christopher Bennage on 10/13/2008 at 1:27 PM
We are experiencing this same problem. It is intermittent for us as well, though seems to happen more frequently when debugging with break points.
Posted by StefanOlson on 10/8/2008 at 5:57 PM
From the validation section of this feedback you should be able to reproduce the issue by pressing alt+tab when the splash screen is displayed. End result is the same as the problem that I'm setting although I've never pressed alt+tab.
Posted by Christoph Hornung on 9/25/2008 at 6:38 AM
We have the same problem in our app, it appears every few starts. Seems to be a Schrödinger Problem as it is not reproducible consistently. (But seems to appear more often on some machines)
Posted by Microsoft on 8/27/2008 at 2:58 AM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. When you are available to send us the additional details that can help us to reproduce the problem, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team
Posted by Microsoft on 8/22/2008 at 1:48 AM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.
It may help if you provide us with:

1. a demo app


If we do not receive a response from you after 7-days , we will automatically close your issue. There is no obligation to respond -- at any time you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team