Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
155
UltraDesktop Alert Memory Exception
posted

Hello,

    I have recently started seeing an exception being thrown from our application within the development environment (VS2008 SP1) when using the alerts. The application displays 2 alerts on start-up, 1 from 2 different UltraDeskTopAlert controls on the form. The 1st displays OK and the second then throws the error stack below.

The only change I can think of is that recetnly we have increased the workstation (XP) memory to 4GB and launched XP using the /3GB switch. Would this affect the controls in any way?

We are using version 8.3.20083.2021.

The exception is thrown from the routine:

 

 

 

 

 

 

 

 

Dim ultraAlert As

Infragistics.Win.Misc.UltraDesktopAlertShowWindowInfo = alertBase.UltraAlertObject

alertBase.SetUltraAlertProviderForMsg(MDIAlertsWarnings)

 

 

If ultraAlert IsNot Nothing AndAlso Not MDIAlertsWarnings.IsOpen(ultraAlert.Key)

Then

 

 

If _setalertDlgWarning Is Nothing

Then

_setalertDlgWarning =

 

New SetAlertDelegateDefWarning(AddressOf

SetAlertDelegateWarning)

 

 

End

If

 

 

Me.Invoke(_setalertDlgWarning, New Object

() {ultraAlert})

 

 

End

If

 

 

   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at CMS.CMSControl.main(String[] args) in W:\EXETERXP14\dev\Source\CMS.NET\ContractManagementSystem\clsMCMControl.vb:line 509

 Inner Trace:

Not enough storage is available to process this command
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at CMS.CMSMdi.DisplayDeskTopAlertWarning(AlertDefWarningBase alertBase) in frmCmsMdi.vb:line 1917

 

Thanks for any help or fix suggestions.

  • 155
    posted

    By the way, the only way to clear the problem is to re-start VS2008.