I am currently using DevExpress but considering switching to Telerik.
I downloaded the Telerik UI for WPF demo version and applied it to my existing application for evaluation. However, I encountered an issue and would like to ask for assistance.
I created a project using the "Telerik WPF Application (.NET Framework)" template, ran the blank project, and resized the window. Since our users work with four 2560x1440 monitors, I resized the window to fill all four monitors.
At this point, the following error occurred:
Unhandled exception of type 'System.OutOfMemoryException' occurred in PresentationCore.dll.
There is not enough memory to continue the execution of the program.
This exception does not occur in Microsoft WPF projects.
Before purchasing, I would like to confirm if there is a solution to this issue.
Thank you in advance for your response.
Hey kihwan, can you tell me what do you mean by saying that you've applied the WPF Demos application to your existing application? Do you mean that you've added the entire source code of the WPF Demos application or only the code of a specific example from the demo? If the issue occurs in a specific example, then can you tell me which one is it? Additional to that, can you tell me if the exception occurs in the WPF demos application itself or only when you copy the code to your application?
Also, it would be helpful, if you can send over the troublesome project. If you don't want to share it here in the forum, you can open a new support ticket from your telerik.com account.
I am currently evaluating Telerik by applying it to our existing application.
During the evaluation process, I encountered an exception when resizing the window. To ensure this issue was unrelated to our existing application, I created a new blank project for testing.
Even with no custom code added, running a Telerik WPF Application (.NET Framework) template and maximizing the window size causes an exception.
The project contains no code written by me, yet the exception still occurs when resizing the window to its maximum size.
I sincerely appreciate your response.
Can you tell me which template you are using when creating the Telerik WPF Application (.NET Framework)?
I am asking this, because using this VS template opens an extra window that allows you to select the actual scaffolding template. If you select Blank, no Telerik code is added, so you are using only standrad WPF components (only a Window in this case). However, you can choose also between several more templates.
If you the issue occurs with the Blank template, can you test the issue also with a standard WPF application created with the default WPF template in Visual Studio - "WPF App (.NET Framework)"?
As you mentioned, I created the project using the Blank template, and even without adding any code, the behavior differs from that of a standard WPF application.
I have attached a screenshot of the project I selected for your reference. Additionally, I’ve included the creation screen of a standard WPF project, where no exceptions occurred.
I have double checked this, but couldn't recreate any errors on multiple monitors with high resolution. Also, the Blank template of Telerik is almost identical with the WPF native template. The only difference is that the Telerik project template references the Telerik.Windows.Controls.dll, but no Telerik code is used or loaded during the runtime.
Can you send over the full stacktrace, so I can check it on my side? This can give some idea on what is happening.
Additional to that can you tell me what is the DPI scaling applied to the monitors (100%, 125%, etc.)?
Also, can you tell me if the exception occurs when the application runs without debugging?
System.OutOfMemoryException HResult=0x8007000E Message=Insufficient memory to continue the execution of the program. Source=PresentationCore StackTrace: at System.Windows.Media.Composition.DUCE.Channel.SyncFlush() in System.Windows.Media.Composition\DUCE.cs:line 241 at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet) in System.Windows.Interop\HwndTarget.cs:line 1403 at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam) in System.Windows.Interop\HwndTarget.cs:line 1295 at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam) in System.Windows.Interop\HwndTarget.cs:line 818 at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) in System.Windows.Interop\HwndSource.cs:line 1103 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) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
Instead, I retrieved Exception information.
DPI is set to 100%.
When I ran the program without debugging, the Exception did not occur.
Even in Release mode in Visual Studio, the Exception occurred, but when I ran the compiled program without Visual Studio, both the Debug and Release versions worked fine.
Thank you for the stacktrace. As I understand this is an issue that can be observed in the WPF native Window component, which seems to need extra memory to get rendered on the specific monitors setup. I found several reports related to this. Note that these are for .NET, but as I understand from some of the comments the same issue can be recreated also in .NET Framework.
What you can try is to use x64 configuration for the project, instead of x84 (if this is your current setup).
Also, if you are using Visual Studio 2019, you can try the latest version of Visual Studio 2022 and see if the issue still occurs.
I’m already using Visual Studio 2022, and after switching to x64, all the issues were resolved.
I've been using SQLite3 for a long time, which is why I’ve been sticking with x86, but now I’m considering switching to x64.
Thank you so much for continuously helping me over such a long period.
Also, I’ve purchased and am using Telerik UI for WPF.
Once again, I really appreciate your help.
Have a great day! 😊
Great to hear that the suggestion with the x64 configuration helped for the problem.
Since now it seems that you have a commercial license (after your purchase), I could suggest you to use the internal support ticketing system if you have questions related to the Telerik product. This way you can take advantage of the dedicated support service and the included 24h response time.