lepoco / lepoco/wpfui

WPF-UI program crashes and becomes unresponsive when dragged to second display on computer with dual monitors.

Open
#619 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
9.6k
Forks
1k
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

When running a WPF-UI program on a computer with two displays, the program works fine on the primary display. However, when the program is dragged to the second display, it crashes and becomes unresponsive.
When an error occurs in Visual Studio, this is a screenshot of the error message displayed for the code demo.
image

To Reproduce

[With Microsoft Store WPF UI App]
0.Connect the computer to two displays.
1.Download WPF UI from the Microsoft Store.
2.Open the WPF UI software (it runs normally on the default screen at this point).
3.Drag the WPF UI to the second screen.
4.Click on any button, and the WPF UI will become unresponsive or crash.

[With Viscual Studio 2022]
0.Connect the computer to two displays.
1.Create a WPF-UI project in Visual Studio.
2.Click on Run or Debug in the newly created project to launch the project file.
3.The generated project runs normally on the default screen.
4.Drag the generated software to the second screen, click on any button, and the software will crash and freeze.
5.The error message displayed in the screenshot appears in Visual Studio.
image

Expected behavior

Expected result: The WPF-UI software should not crash or become unresponsive when dragged to any screen

Screenshots

No response

OS version

Windows11
Default screen resolution
1920 x 1080
125%

The second screen
1920 x 1080
100%

.NET version

.NET 6.0

WPF-UI NuGet version

2.0.3

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are identified. Reproduce the crash with two displays using the Microsoft Store app or a generated Visual Studio 2022 WPF-UI project, then inspect the Visual Studio error shown in the report. Done means the application remains responsive when moved to the second display and buttons can be used normally.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.