Issue with Windows Chrome on Windows 8 64 bit - by srinikat

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 742603 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/17/2012 5:34:23 PM
Access Restriction Public


We have a WPF System Tray Application, our application is using Borderless Window to display the main window.  Our Application uses VB based technique for making our application single instance application.  Our application uses lot of PNG graphics.  

Our MainWindow stops rendering and displays black window when the application is activated from the second instance. 

Typical scenario is 
1) We launch the application from the Control Panel. 
2) Close it to system tray
3) Again go back to Control Panel and Launch second instance it from there. 
At this point of the point of time the first instance gets activated but the main window is displayed as black rounded rectangular window. 

The laptop is based on Intel HD Video Chipset.  Please see DxDiag report attached. 

Long time ago we gave up on WPF Layered windows Solution, Microsoft is supposed to follow up on this issue but we still see these issue with .NET 4.0

At this point of time we are using Region Windows and Chrome Windows Solution which is official solution in .NET 4.0. 

Please note that we see this issue with Windows Chrome Solution too.  

******* This is a showstopper for us and our ODM Customer *****.  We need some solution or workaround for this. 

Please see attached screen capture of our application and DxDiag information.  

Sign in to post a comment.
Posted by Microsoft on 5/22/2012 at 5:01 PM
Thanks for the information. Looking at the history of the closed issue, the WPF graphics team determined the issue was display driver related. When that is a question, you can force WPF to render through software to troubleshoot that. I see the message about this being an issue in your component. I will close this. Thank you.
Posted by srinikat on 5/18/2012 at 5:34 PM
This seems to be issue with our own component, you can close this issue for now. I will reopen this issue if
we see the issue again.
Posted by srinikat on 5/18/2012 at 1:05 PM
yes, we also tried switching back to WPF Layered Windows with the same repro-scenario we ended seeing following error

System.Runtime.InteropServices.COMException was unhandled
Message=UCEERR_RENDERTHREADFAILURE (Exception from HRESULT: 0x88980406)
     at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
     at System.Windows.Media.MediaContext.CompleteRender()
     at System.Windows.Interop.HwndTarget.OnResize()
     at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
     at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(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, Int32 numArgs)
     at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
     at System.Windows.Threading.DispatcherOperation.InvokeImpl()
     at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
     at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
     at System.Windows.Threading.DispatcherOperation.Invoke()
     at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherOperation operation, CancellationToken cancellationToken, TimeSpan timeout)
     at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
     at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
Posted by MS-Moderator10 [Feedback Moderator] on 5/18/2012 at 3:41 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by MS-Moderator01 on 5/17/2012 at 10:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(