-
Notifications
You must be signed in to change notification settings - Fork 693
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
Enable in-app Toolbar in XAML Hot Reload crashes in App SDK 1.4 #8806
Comments
I see the same issue. Here is a stack trace:
|
Turning off the "Enable in-app Toolbar" fixes this issue for me, so you can still use XAML Hot Reload |
Seeing the same behaviour - Disabling the 'Enable in-app Toolbar' avoids the crash |
Thanks, it also fixes the issue for XAML Islands in WPF which crashed with "access violation", while the same code worked in WinForms |
@JoeTomkinson this is not closed - the duplicate #8848 was |
Apologies, was viewing this on mobile to check the status and clearly misread. |
Same issue here... and now my front-end developers aren't happy with us upgrading to 1.4. So it's pretty blocking for us! |
internal MS issue: https://task.ms/47919577 |
@JoeTomkinson so I guess this is actually closed now. |
@llongley what's the dupe? We're still waiting on this and it's blocking us moving to 1.4 |
This issue was addressed in Visual Studio version 17.8 |
@Scottj1s thank you for your answer, but could you clarify that? Because I just tried it and still get the issue. I'm running visual studio 17.8.6.
that's the same behavior as before, so I don't see how it's "completed"? Like said: our front-end developers are using that toolbar, so they don't want us to switch to 1.4 this way. It's still blocking us. |
I just wanted to confirm that at my company we are seeing the same issue. We're running visual studio 17.8.5. We have over 50 developers with the same issue here. |
@irperez @JochemPalmsens While the in app toolbar does still have this issue. We've been able to work around this using the "Live Visual Tree" window in visual studio. The toolbar there has many of the same functions (if not all) as the in app toolbar and still works without issue. @Scottj1s @llongley This issue still exists in VS 2022 17.8.6 and has not been addressed. One of these issues should be re-opened. |
I just tried it with the new Visual Studio 2022 releases today:
So apparently it was addressed in 17.9, not 17.8... but it's not fixed Details: It's more that it sometimes seems to work in 17.9, but sometimes also doesn't. Update 19-2-2024: we made all colleagues update to Visual Studio 17.9 and rolled out a test update to WinAppSDK 1.4. Even after thorough cleaning of build directories, almost everybody had problems with the in-app toolbar, so we need to stay at WinApp SDK 1.3 until this is really fixed. @Scottj1s So it seems there still are issues. |
@irperez , @JochemPalmsens , @NicholasChrzan - thanks all for your feedback. We're engaging with the Visual Studio team to root cause. I was unable to repro this myself, after updating to VS 17.8+. But evidently, you all are still seeing the crash on latest VS. |
This crash was manifesting from two location:
I don't understand why the crash still repros with VS 17.8+. The Visual Studio team has requested a VS feedback item, ideally with a repro project, and at minimum a crash dump. In addition, the hardening in Windows App SDK 1.5 should also resolve this crash, so upgrading is another option. |
Just to confirm what we're seeing, below are the versions we're using. I didn't provide enough detail. Related VersionsVisual Studio Professional 17.8.5. From the About Dialog:Microsoft Visual Studio Professional 2022 Installed Version: Professional Visual C++ 2022 00476-80000-00000-AA140 ADL Tools Service Provider 1.0 ASA Service Provider 1.0 ASP.NET and Web Tools 17.8.358.6298 Azure App Service Tools v3.0.0 17.8.358.6298 Azure Data Lake Tools for Visual Studio 2.6.5000.0 Azure Functions and Web Jobs Tools 17.8.358.6298 Azure Stream Analytics Tools for Visual Studio 2.6.5000.0 C# Tools 4.8.0-7.23572.1+7b75981cf3bd520b86ec4ed00ec156c8bc48e4eb Common Azure Tools 1.10 Copy Nice 1.0.7 CreateUnitTestBoilerplateCommand Extension 1.0 File Differ 3.0.49 File Icons 2.7 Fine Code Coverage FineCodeCoverage2022.ad53fb28-7a11-4465-a27a-3550499ea4a1 GitHub Copilot 1.137.0.0 (v1.137.0.0@2f127d06d) GitHub Copilot Agent 1.137.0 ILSpy.AddIn 1.0 Insert Guid 1.3.6 Microsoft Azure Hive Query Language Service 2.6.5000.0 Microsoft Azure Stream Analytics Language Service 2.6.5000.0 Microsoft Azure Tools for Visual Studio 2.9 Microsoft JVM Debugger 1.0 NuGet Package Manager 6.8.0 Office Developer Tools for Visual Studio 17.6.34024.01 Rainbow Braces 1.0.155 Razor (ASP.NET Core) 17.8.3.2405201+d135dd8d2ec1c2fbdee220e8656b308694e17a4b Snippet Designer 1.8.1 SQL Server Data Tools 17.8.120.1 Test Adapter for Boost.Test 1.0 Test Adapter for Google Test 1.0 ToolWindowHostedEditor 1.0 TypeScript Tools 17.0.20920.2001 Visual Basic Tools 4.8.0-7.23572.1+7b75981cf3bd520b86ec4ed00ec156c8bc48e4eb Visual F# Tools 17.8.0-beta.23475.2+10f956e631a1efc0f7f5e49c626c494cd32b1f50 Visual Studio IntelliCode 2.2 Workflow Manager Tools 1.0 1.0 |
@Scottj1s VS 17.9.0 |
Sorry for the confusion, and thanks for the repro @Prochy - very helpful. I've confirmed that the fix is in the WinAppSDK 1.5 release candidate (and not in Preview 1). |
Well that's good news... although we have no way to test if it works for our projects yet. I guess we'll have to wait. When is the RC released? In the meantime I made a minimal test solution (to compare 1.3, 1.4 and 1.5): https://github.com/JochemPalmsens/WinAppSDKbug8806 Just adding a second window on launched triggers the bug. |
I can confirm that (at least it seems so) it's fixed in 1.5.240227000 |
I see this crash happening all the time in App SDK 1.6 when closing (child)Windows. Hot Reload is broken for me. |
Describe the bug
When debugging windows app sdk (1.4.230822000) with visual studio 202217.7.3 I get an access violation when opening
our application after about 10 seconds, Turning off the "Enable in-app Toolbar" under the XAML hot reload allows the app to start and not crash.
From the crash log:
ExceptionAddress: 00007ffd6057de84 (Microsoft_UI_Windowing_Core!Api::ReunionApi32::GetWindowFeatureImpl+0x0000000000000020)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000001
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000030
Attempt to read from address 0000000000000030
Steps to reproduce the bug
Start app in x64 debug in VS 2022 17.7.3
Open second window
Crash
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.4.0: 1.4.230822000
Windows version
Windows 10 (21H2): Build 19044
Additional context
No response
The text was updated successfully, but these errors were encountered: