lepoco / lepoco/wpfui

Managed Debugging Assistant 'PInvokeStackImbalance' : 'A call to PInvoke function 'Wpf.Ui!Wpf.Ui.Interop.User32::SetWindowLong' has unbalanced the stack. This is likely because the managed PInvoke signature does not match the unmanaged target signature. Check that the calling convention and parameters of the PInvoke signature match the target unmanaged signature.'

Open
#738 2 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

I have this incredibly simple code that throws an exception:

using WpfUi = Wpf.Ui;

namespace Redacted.Replay.Gui.Wpf.ViewModels
{
    public class PatientViewModel
    {
        public void ShowError()
        {
           new WpfUi.Controls.MessageBox().Show();
        }
    }
}

The exception:

Managed Debugging Assistant 'PInvokeStackImbalance' : 'A call to PInvoke function 'Wpf.Ui!Wpf.Ui.Interop.User32::SetWindowLong' has unbalanced the stack. This is likely because the managed PInvoke signature does not match the unmanaged target signature. Check that the calling convention and parameters of the PInvoke signature match the target unmanaged signature.'

Interestingly, I didn't throw any exception initially. Not sure what change made this error appear.

To Reproduce

Create project Redacted.Replay.Gui.Wpf. Add following code:

using WpfUi = Wpf.Ui;

namespace Redacted.Replay.Gui.Wpf.ViewModels
{
    public class PatientViewModel
    {
        public void ShowError()
        {
           new WpfUi.Controls.MessageBox().Show();
        }
    }
}

Call new PatientViewModel().ShowError();

Expected behavior

No error. The MessageBox should display.

Screenshots

No response

OS version

Windows 11.

.NET version

4.8.1

WPF-UI NuGet version

2.1.0

Additional context

For what it's worth, both WPF UI and my project have Wpf in the namespace. Changing .Show() to .ShowDialog() works properly.

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

The report points to Wpf.Ui.Interop.User32::SetWindowLong and the Wpf.Ui.Controls.MessageBox.Show path; start by locating that interop declaration and tracing the call made by Show(). Reproduce the managed debugging assistant under the stated Windows 11, .NET 4.8.1, and WPF-UI 2.1.0 setup, with completion verified when Show() displays the message box without the stack-imbalance error.

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.