WLP 6.9.17 exits unexpectedly with Windows 8.1 PC
Author: haytac
Creation Date: 4/30/2017 9:53 PM
profile picture

haytac

#1
Hi,
Downloaded 6.9.17 on multiple machines.
So far Windows 10 systems run fine
On one Windows 8.1 system: WLP exits after 40 minutes to 2 hours.
Thanks!
profile picture

Eugene

#2
Hi,

There's not enough information. Probably defective RAM or HDD?
profile picture

haytac

#3
Thanks for quick response!

HW failure coincident with 6.9.17 upgrade is low probability.
Daily runs with earlier WLP version did not see this issue since 2012.
What kind of information would you like me to provide?
Will research to see if Windows provides info when it shuts down a program (or does WLP shut itself down?)

Here is the wlp.txt output for that day: except for one case the messages appear to be the same issue as another recent post.
2017-04-27 12:13:41,637 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:41,918 [15] ERROR WealthLab.DataProviders.FidelityStaticProvider [(null)] - Abort called on thread. A user running a strategy could want to abort the thread.
System.Threading.ThreadAbortException: Thread was being aborted.
at WealthLab.Bars.LoadFromFile(String fileName, DateTime startDate, DateTime endDate, Int32 maxBars)
at WealthLab.BarDataStore.LoadBarsObject(Bars bars, DateTime startDate, DateTime endDate, Int32 maxBars)
at WealthLab.BarDataStore.LoadBarsObject(Bars bars)
at WealthLab.DataProviders.FidelityStaticProvider.a(Bars& A_0, Bars A_1)
at WealthLab.DataProviders.FidelityStaticProvider.RequestData(DataSource ds, String symbol, DateTime startDate, DateTime endDate, Int32 maxBars, Boolean includePartialBar)
2017-04-27 12:13:44,824 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:45,825 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:46,840 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:47,856 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:48,888 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:49,903 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:50,903 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:51,904 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:52,904 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:54,065 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:55,078 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
2017-04-27 12:13:56,090 [Managed End Point thread 1] ERROR WealthLab.DataProviders.FidelityACTIVStreamingProvider [(null)] - OnConnectFailed(() - Connection to Activ server failed. Reconnecting using asynchronous login.
profile picture

Cone

#4
QUOTE:
What kind of information would you like me to provide?
Wealth-Lab environment. Open tools, charts, etc. Streaming? Did it occur when you pressed a button, opened a chart, etc.?
profile picture

Eugene

#5
Thanks for the details, Haluc. At first glance, not detecting any obvious reasons in this log.

The information I'm looking for is:

1. Is this a repeatable event? How can we reproduce it?
2. How exactly does it exit? Is there a post-crash message?
3. What is the exact workflow? What Wealth-Lab tool(s) is being run when it crashes? What do you do when it happens?
4. Does it take place when your specific Strategy is working or it can be any built-in Strategy? The same with other WLP tools e.g. SM, chart window, Quotes, Accounts etc.

Here's a couple of hints I can offer:

1. Examine if any 3rd party program (scheduler, custom utility, antivirus etc) can be shutting down WLP for any reason, intended (like automatic memory management) or unintended.

2. Since you develop huge strategies of 130K lines which as we believe may crash WLP themselves*, debugger in Visual Studio or SharpDevelop is your best friend. Attach to process and wait for crash. Examine the unahandled exception message or stack trace when it appears.

* Face it please: we don't know what code they contain. I can easily imagine a scenario with advanced programming when some code (e.g. using Reflection) is called from time to time and that failing due to a slight change (e.g. obfuscation signature in WLP).

3. While the probability of H/W failure may be low, in my support experience it is real and may look exactly like this - just WLP/D is crashing while other software runs fine.

The more details the better the chances to track the problem down and help you.
profile picture

haytac

#6
Hi, thanks for your inputs.

I ran a number of experiments and found that the memory footprint of WLP 6..9.17 is much larger in Windows 8.1 than Windows 10.

- Memory footprint data from Task Manager
- SONY 8GB RAM i7 1.76GHz CPU, Windows 10: 1.5GB of RAM utilized
- SONY 8GB RAM i5 2.4 GHz CPU, Windows 10: 0.5GB of RAM utilized
- HP 8GB RAM, i7 3.4GHz CPU, Windows 8.1: 4.6GB of RAM utilized
- I am runing WLP with a C# options trader program
- If this program is run from within Visual Studio the failure occurs earlier than when running as standalone app.
- My guess is that WLP shuts down because of OOM (out of memory)

As Windows 10 is a later version than 8.1 and it works I consider the issue resolved.

Still the wide range of numbers, even within Windows 10 machines, is remarkable.

Would you have a guess as to why this is?

Thanks and Regards,
profile picture

Cone

#7
Different machines? Then it's likely that you didn't launch Wealth-Lab with the same...
1. script library
2. extensions
3. workspace

It just doesn't seem to me that the measurements were observed under the same controlled conditions. I have many extensions and scripts installed, and loading a blank workspace comes in only at 92Mb.

And, what's the mysterious C# options trader program?

I don't know what's causing crash(es) in 6.9.17, but I don't think they are due to a memory issue.
profile picture

Eugene

#8
@Cone

QUOTE:
And, what's the mysterious C# options trader program?

Maybe this one - since 2010? Options trading with C#

This is why I turn skeptical when I hear about mysterious issues from a developer: we've got all the rope to shoot ourselves in the foot. ;)
profile picture

haytac

#9
Wow! Have I been at it this long? Guess I am closing in on the proverbial 10,000 hours. As WLP does not place options orders, I do this with a C# program. These two communicate via files. The three machines were all upgraded to 6.9.17. Strategies folder had the same content.

Thank you for all your help. I hope WLP is around for many years to come and you two are not retiring any time soon. Just starting to get the benefits of my work. I came to appreciate WLP's value, the effort that must have gone into architecting and coding it.