- ago
After I canceled Run Backtest, WealthLab became very slow. I restarted the program WealthLab 8 Build 30, and the entire strategy was suddenly deleted, no more entries and the following error message:



When I press any button WealthLab 8 crashes completely, nothing works anymore.

Interestingly, when I open another workspace and manually reload the strategy, everything is back.

Here is the entire error message:
System.NullReferenceException: Object reference not set to an instance of an object.
at WealthLab8.designerBuildingBlock.UpdateStrategyFromUI()
at WealthLab8.cwStrategy.PushAttribute()
at WealthLab8.cwStrategy.AllowWindowClose()
at WealthLab.WPF.ChildWindow.SetObserver(Object asset, CancelEventArgs map)
at WealthLab.WPF.MDIChild.Close()
at WealthLab.WPF.MDIChild.DestroySystem(Object key, RoutedEventArgs cont)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Controls.Primitives.ButtonBase.OnClick()
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(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)


Regards Christian
0
376
6 Replies

Reply

Bookmark

Sort
- ago
#1
It's not that 'build 30 is very unstable' so I've renamed your overly assertive topic title. The reason is not yet determined. I suppose if you click Continue then WL8 should start because the exception is handled gracefully. Presumably the strategy file is corrupt. We could try to determine what goes wrong if you send its XML file to support@wealth-lab.com:

c:\Users\%Windows username%\AppData\Roaming\WealthLab8\Strategies\
0
- ago
#2
Hm it is very frustrating when I want to close the strategy with 'X' and the whole WealthLab crashes, the button continue does nothing here. I can't even delete the strategy from the current workspace, after the crash all blocks have been deleted.

I will send the xml file to the support.

Regards Christian
0
Cone8
 ( 23.92% )
- ago
#3
It looks like the strategy is just buy/sell market. If you ran the strategy on many bars and/or many symbols, it's possible you ran into a memory limitation due to the creation of perhaps tens of thousands of positions.
0
- ago
#4
@Cone - no, the strategy has several blocks in it. It's just that when a Blocks strategy becomes corrupt, conditions fail to load and may create such impression.

Christian, the strategy has loaded just fine for me. You mention 'another workspace' (which works) so I assume we need more details to reproduce.
0
- ago
#5
Now this is pure speculation (without knowing Christian's strategy)...could it be that something no longer works on Windows 10 as it does on Windows 11 (as I mentioned in a previous post... the upgrade solved my similar problem with NullReference)?
0
- ago
#6
Everything WL8 is still working on Windows 10 here but the context of your issue was pretty different from topic starter's.
0

Reply

Bookmark

Sort