You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.
WindowsXamlHost hosts CaptureElement, The time between InitializeComponent() and triggering CaptureElement.Loaded event is 7.4 sec for WindowsXamlHiost v 6.1.2, but the same time for WindowsXamlHiost v 5.1.1 is less than 0.4 sec,
CaptureElement_Loaded tgriggers in 7.4 sec for WindowsXamlHost v.6.1.2 and in 0.3 - 0.4 sec for v. 5.1.1.
Test for 6.1.2. was done with NuGet packets. It took 7.4 sec
Then to test with 5.1.1 the reference to Windows.Foundation.UniversalApiContract was replaced by refence to Windows.winmd v 10.0.19041.0 (C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.19041.0\Windows.winmd) With this replacement the time for WindowsXamlHiost v 6.1.2 remains the same. But when I change reference to WindowsXamlHiost v 5.1.1 I got 0.3 sec
OS: Windows10 22H2.
Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work: 5.1.1
Steps to Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
It is expected that window loading takes 0.4 sec as it was for v 5.1.1 but not more than 7 sec.
Screenshots
If applicable, add screenshots to help explain your problem.
Hello Eugen00-00, thank you for opening an issue with us!
I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌
Eugen00-00
changed the title
Performance issue WindowsXamlHost v6.1.2 when its child is CaptureElement (but there is no issue with v. 5.1.1)
Performance issue WindowsXamlHost v6.1.2 if its child is CaptureElement (but there is no issue with v. 5.1.1)
Mar 12, 2023
Describe the bug
WindowsXamlHost hosts CaptureElement, The time between InitializeComponent() and triggering CaptureElement.Loaded event is 7.4 sec for WindowsXamlHiost v 6.1.2, but the same time for WindowsXamlHiost v 5.1.1 is less than 0.4 sec,
Code:
Main window has the only element in the grid:
MainWindow.xaml.cs:
CaptureElement_Loaded tgriggers in 7.4 sec for WindowsXamlHost v.6.1.2 and in 0.3 - 0.4 sec for v. 5.1.1.
Test for 6.1.2. was done with NuGet packets. It took 7.4 sec
Then to test with 5.1.1 the reference to Windows.Foundation.UniversalApiContract was replaced by refence to Windows.winmd v 10.0.19041.0 (C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.19041.0\Windows.winmd)
With this replacement the time for WindowsXamlHiost v 6.1.2 remains the same. But when I change reference to WindowsXamlHiost v 5.1.1 I got 0.3 sec
OS: Windows10 22H2.
Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
It is expected that window loading takes 0.4 sec as it was for v 5.1.1 but not more than 7 sec.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: