Reentrancy crash destroying a TextBox due to its ShutdownTextServices() call #9070
Labels
area-TextBox
TextBox, RichEditBox
bug
Something isn't working
closed-Fixed
Described behavior has been fixed.
team-Controls
Issue for the Controls team
Milestone
Comments
codendone
changed the title
|
Thanks for providing the stowed exception stacks, @jhert0! This shows a reentrancy crash triggered by CTextBoxBase::Destroy calling ShutdownTextServices which makes some COM calls:
This is a mirror of an internal bug found a few days ago where the InitializeTextServices() call can also cause a reentrancy crash. We should make sure both are fixed together. |
codendone
added
area-TextBox
|
@codendone Do you guys know when these fixes could be released? We have been encountering a lot of random crashes with our application, the vast majority are either impossible or extremely difficult to reproduce, and most of the crashes dumps are useless because they were before we turned on the full dump and they were generated from stowed exceptions. |
Any updates on this issue? |
|
Our user just encountered this again, there are other stowed exceptions that don't look like they are related so I don't know if you want me to open other issues for them but here is the stack trace: |
|
@jhert0 The other stowed exceptions there have different HRESULTs and appear unrelated, so it these must have been handled and can be ignored. XAML stows many error codes it sees just in case they are needed to help debug a fatal issue. In this case, the first stack from this more recent dump shows the same ShutdownTextServices() issue, which is all that matters. For timeline, there isn't any info yet to share. The bug has been assigned and once there is a fix we can evaluate if it is safe to service to 1.4. |
@codendone I can confirm that the issue appears to still be happening in the first experimental build of 1.5. |
|
I was wondering if this was fixed in 1.5 or if there is an update on when this will be fixed? |
|
We're on WindowsAppSdk 1.5.5, self-contained, unpackaged app, and experiencing a similar issue. Our customers are suffering random crashes on our application from time to time. The application just dissapears without ceremony, leaving behind only a Windows Event entry. Once I was able to reproduce the problem having WinDbg attached to the process, so I have the stacktrace and WinDbg output. The stacktrace looks very similar to the parent post, but who knows with those stowed exceptions: WinDbg command output by the time the app crashed. That 'ImageDecodeActivity' before crashing would point to any other problem, I don't know. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Stowed exception thrown after navigating back resulting in the app crashing.
Steps to reproduce the bug
Have not been able to reproduce. Happened on a users computer.
Expected behavior
No crashes.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.4.2: 1.4.231008000
Windows version
No response
Additional context
App is packaged and the user is running Windows 11 23H2.
The text was updated successfully, but these errors were encountered: