My system: WL 6.5 64-bit, Quad core, 12 Gig memory.

I'm getting the following output from log file (C:\Users\Owner\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Logs\wlp.txt) before WL crashes.

a few of these outputs:
2013-09-23 09:39:54,803 [1] ERROR WealthLabPro.ChartForm [(null)] - Overflow error.

then few of these outputs:
2013-09-23 09:42:08,472 [EMS Session Dispatcher (512453)] ERROR WealthLab.DataProviders.FidelityBrokerProvider [(null)] - Error in Shadow post alert for Balances SPBSM
System.NullReferenceException: Object reference not set to an instance of an object.
at WealthLab.DataProviders.FidelityBrokerProvider.a(XmlDocument A_0, String A_1, String A_2)

then this output pops up whenever I open the Data Manager:
2013-09-23 09:48:09,821 [68] ERROR Fidelity.Components.RequestManager.FidelityWebService [(null)] - Failed to fire OnWatchListGet event: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at Fidelity.Components.RequestManager.WatchListGet.DoCallback()

then after few minutes, it crashes.

The crash may or may not have anything to do with the above outputs but I just want some ideas what they could be. So what are these errors and should I be concerned?

It's also possible my script is messed up or my watchlist symbol data error is causing the crash.

QUOTE:
It's also possible my script is messed up or my watchlist symbol data error is causing the crash.

I also think so. The first two handled exceptions 10 minutes before the event are unlikely to have an impact here. The closest one (i.e. interacting with a form element that does not exist yet) looks suspicious but not necessarily produces crashes (although it can). It's likely an indication of a programming oversight: a control was accessed from a different thread in a not so failsafe manner.

Can you reproduce this crash reliably? What exact steps are you doing to make it happen? How does your script look like, and what's your DataSet? The key is being able to reproduce.

I have managed to duplicate the last error consistently. (ie ERROR Fidelity.Components.RequestManager.FidelityWebService [(null)] - Failed to fire OnWatchListGet event)

1 Start WL fresh.
2 Scale: Daily; Data Range: 400 Bars; Position Size: $10,000(RP)
3 Log into Fidelity.
4 Open a New Strategy from Code Chart (make sure it's streaming).
5 Choose symbol AA or any Dow symbol.
6 Open Data Manager and then just close it.
7 Error will show up in C:\Users\Owner\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Logs\wlp.txt

But of course, this error doesn't necessarily crash anything. But, when I have multiple Workspaces (like 5 or 6) open and then I try to open and close the Data Manager, it will crash the WL sometimes immediately or sometimes little later.

Thanks for the steps. I only tried to reproduce it with WLD without enthusiasm (because FidelityWebService is obviously not at play here), having 4 workspaces open and streaming Yahoo data. Unsuccessfully, of course. More tests with WLP are required.

So should I open up a ticket and include a copy of wlp.txt?

It's not required. I can duplicate the Data Manager handled exception in WLP with the procedure - although Streaming wasn't required. This one seems pretty innocuous (can be ignored). I'm guessing that it has something to do with the Fidelity Provider initializing the WebService used to import a Watchlist from fidelity.com when creating a new DataSet, however, the "Create new DataSet" Window hasn't been created (since you're not even doing that).

Anyway, this alone isn't causing a crash (at least not for me), but I'll send a message to the responsible developer to see if it's worthwhile cleaning up. It may in fact be part of the code design. Sometimes exceptions are expected, and then they are handled gracefully.


Note!
AA is no longer in the Dow 30. As of today, NKE, GS, V replaced BAC, HPQ, AA. The current Dow 30 constituents are:

CODE:
Please log in to see this code.

I also tend to think that since the exceptions are handled and do not have a direct relationship with the crash, it (crash) might be caused by richard1000's script, for example.

If you don't have Visual Studio to debug WLP when it crashes (which is the preferred way to avoid any trial and error), consider wrapping your strategy's code in a try/catch block:

CODE:
Please log in to see this code.

Also, try excluding all drag and dropped indicators if you have them - e.g. by copying/pasting into a blank strategy window and saving. There may be some issue, too.

Ok, I tried something else and it definitely crashed for sure.

1 Set Scale: Daily; Data Range: 400 Bars; Position Size: $10,000(RP)
2 Log into Fidelity.
3 All the Performance Visualizer preferences checked except Portfolio Inspector
4 Open 40 chart script of "Glitch Index" (set to streaming but it may not matter)
5 Choose 40 Nasdaq100 symbols.
5 Save as workspace
6 Try to open two copies of workspace and will crash

So in essence I tried to open 80 strategy windows pointing to 80 symbols. So besides hardware limitations, is there a software limitation on how many chart scripts I can open?

Some performance visualizer might have a bug that makes it crash. Firstly, update all visualizer libraries to their latest versions. Next, try isolating the bug. To do that, uncheck all visualizers, and start opening windows. If it's OK, close the windows. Repeat the cycle, adding visualizers one by one until you can reproduce the crash.

Note: when you open a saved workspace, Wealth-Lab restores whatever active visualizers there were when you saved it. Current settings do not apply.