Is it only me who has issues with wl7 freezing. WL often (very) gets into “not responding” state (window state), nothing moves including “Running Backtest…” indicator. The strategy is nothing complex, dow30 e.g. D1 TF. I didn’t get the idea of the context of this freezing. I run backtest several times – one of them can cause this. Or simple strat changes – something like: GetPositions().Count instead of: GetPositions(), or choosing different dataset – as I’ve already mentioned I didn’t get the idea of the correlation. If it takes seconds backtesting with my strat-dataset-PC the ‘not responding’ can last for minutes – I’m not really sure, whether it unfreezes and when. While ‘not responding’ only one CPU core is loaded. All the same both on my desktop and laptop.
Rename
Hmmm no that's not something I've experienced personally, but when it happens is there anything written to the event log (under Tools menu)? Also, what Historical and Event Providers do you have selected? It could be something related to one of those Providers.
I guess I shouldn't put:
touch_window = Parameters[0].AsInt;
or even
sma = SMA.Series(bars.Close, 125);
in Execute() method
:)
Now it works. I hope that was the only reason).
touch_window = Parameters[0].AsInt;
or even
sma = SMA.Series(bars.Close, 125);
in Execute() method
:)
Now it works. I hope that was the only reason).
By the way, my laptop running WL after long time waiting generated this:
12.03.2021 22:14
WL7
Недостаточно квот для обработки команды.
Win32Exception
Недостаточно квот для обработки команды.
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)
12.03.2021 22:14
WL7
Недостаточно квот для обработки команды.
Win32Exception
Недостаточно квот для обработки команды.
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)
Those statements should not really be a problem. If you want to share a full script via email to help diagnose any issues feel free to send it to support@wealth-lab.com.
The Win32Exception "Not enough quota" in your post # 3/12/2021 10:08:13 PM is actually a Microsoft WPF issue:
https://github.com/dotnet/wpf/issues/137
https://github.com/dotnet/roslyn/issues/9247
It's not strategy induced I believe but we'll investigate.
https://github.com/dotnet/wpf/issues/137
https://github.com/dotnet/roslyn/issues/9247
It's not strategy induced I believe but we'll investigate.
Thanks for emailing us your strategy, I figured out the problem! You're strategy is posting a huge number of strings to the Debug log, about 64,000 :) That's what's causing the bottlenecks. I made some changes to handle this better in Build 2, but you can cut back the Debug strings for now to stop this issue.
Great! Both that you've discovered the problem so fast and you've provided an immediate decision.
Your Response
Post
Edit Post
Login is required