Skip to content
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

Insufficient Memory exception #439

vsfeedback opened this Issue Mar 13, 2019 · 0 comments


None yet
1 participant
Copy link

vsfeedback commented Mar 13, 2019

VSF_TYPE_MARKDOWNA WPF Application starts on a dell XPS with a screen resolution of 3840 x 2160. The scale and layout is set to 250% (recommended).
The application starts from Visual Studio 2019 Preview in Debug Mode on the notebook screen and works as expected.
Now I move the application window to a secondary monitor with the same resolution 3840 x 2160 but with scale set to 100%.
As soon as the application goes full screen, the application runs into an uncaught exception:
>Insufficient memory to continue the execution of the program.

> at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
> at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet)
> at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam)
> at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
> at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
> at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
> at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
> at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
> at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

This is what I have tried so far:
A empty WPF application with just a main window does not have the same problem.
The same application that runs into the Insufficient memory problem started from outside of Visual Studio does not have the same problem.
The same application started in Debug mode in Visual Studio 2017 also runs into the insufficient memory problem.

So it seems to be a problem that occurs with this particular application when run in Debug mode on a 4K monitor in both VS 2019 and VS 2017.

This issue has been moved from
VSTS ticketId: 819184

These are the original issue comments:
(no comments)
These are the original issue solutions:
(no solutions)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.