-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Writing to CoreWebView2SharedBuffer times out #3108
Comments
@Take-A-Byte, while we investigate it, could you try to use alternative ways to work around the issue by using the following code instead of
|
@LiangTheDev I tried this out and it works fine. Thanks for the suggestion 🙇 I am trying to find what is the difference between StreamWriter and DataWriter and what are guidelines on which to use when but I could not find anything in Microsoft docs so far. If you know any place I can look for the answer or if you could shed some light on this topic, I would love to know about it :) |
These is due to some subtlety in the WinRT to .NET stream adapter object returned from AsStreamForWrite(). DataWriter is a native Windows WinRT API that works better with other WinRT APIs. Developers should not be concerned with these and therefore it is not documented. |
@LiangTheDev Thanks for the explanation. 🙇 |
Fixed in runtimes 111.0.1615.0+. Thanks! |
Originally posted by @Take-A-Byte in #5 (comment)
Moving to its own new issue.
(Text extracted from image)
Exception User-Unhandled
System.lO.lOException: 'The message filter indicated that the application is busy.
A COM call (IID: method index: 5) to an ASTA (thread
18420) appears deadlocked and was timed out'
Inner Exception
Exception: The message filter indicated that the application is busy
A COM call (IID {0000000C-0000-0000-C000-000000000046}, method index: 5) to an ASTA (thread
18420) appears deadlocked and was timed out.
AB#42876135
The text was updated successfully, but these errors were encountered: