WLP 5 Very slow to load
Author: bobydesi123
Creation Date: 2/15/2010 3:34 PM
profile picture

bobydesi123

#1
Hi,
My WLP is very slow to load, it takes about 30 seconds. I have changed default WS so that NO strategy is loaded on startup. It has been happening for a while. Have very fast laptop with SSD, i dont think it is laptop performance issue. The task manager shows the WLP process starting instantaniously on WLP startup and WLP process is removed from task manager as fast. Follwing is two distinct Windows error reporting information from control panel.
1) The following seems to happen quite often.
Product
Wealth-Lab Pro

Problem
Stopped working

Date
2/11/2010 11:30 AM

Status
Not Reported

Problem signature
Problem Event Name: BEX
Application Name: WealthLabPro.exe
Application Version: 1.0.0.0
Application Timestamp: 4b154f94
Fault Module Name: StackHash_cc95
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00000000
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
Additional Information 1: cc95
Additional Information 2: c375e54b580758c5171c5edeebc4486f
Additional Information 3: 9985
Additional Information 4: 660f15f87bca742dd270e5a01807ca42

Files that help describe the problem
Version.txt
AppCompat.txt
memory.hdmp
minidump.mdmp

2) I dont see this (screen below) often, just today. Probably not related.
Product
Wealth-Lab Pro

Problem
APPCRASH

Date
2/15/2010 2:48 PM

Status
Not Reported

Description
Stopped working

Problem signature
Problem Event Name: APPCRASH
Application Name: WealthLabPro.exe
Application Version: 1.0.0.0
Application Timestamp: 4b154f94
Fault Module Name: mscorwks.dll
Fault Module Version: 2.0.50727.3603
Fault Module Timestamp: 4a7cd88e
Exception Code: c0000005
Exception Offset: 0001c5a7
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

profile picture

Eugene

#2
It's definitely not a performance issue - WLP crashes. Furthermore, the faulting module is one of Microsoft's .NET core DLL.

The most important and missing link: what are you doing when it crashes? Is streaming enabled?

Meanwhile, try the following:

1. Uninstall WLP.
2. Go to Program Files, open Fidelity Investments folder.
3. Remove any DLLs etc. left

4. Repair your .NET installation.
profile picture

bobydesi123

#3
Eugene,
Usually the WLP does not close properly when I exit. Except for known fidelity problems during streaming ( e.g. No ghost bar after 1st tick) WLP works fine. It loads very slowly and does not close properly. This is a real problem when using VS2008 for debugging.
I also suspect that it has something to do with DLLs in WLP directory. Before I follow steps u suggested, please confirm/comment on following.
1. Uninstall WLP - This does NOT affect my data/strategy etc. as they are in appdata folder?
2,3 - I had downloaded and istalled indicators and components, extentions (DLL) from Wiki, Do i have to reload/install them all? If I delete DLL do i have to unregister them?
4. Repair .NET - I have clean VISTA 64 premium with authentic VS2008, this should have a proper .NET(3.5) installed, correct?
profile picture

Eugene

#4
It's quite important thing that you're doing development in VS. This might be the key. btw, are you using COM interop in your compiled code? The error message you're getting is pretty specific. See for yourself:

http://www.google.com/search?q=mscorwks.dll+c0000005

Here goes the updated battle plan:

1 - Disregard.
4 - Disregard.

2,3 - Open the WLP main folder, and delete all your own PDB and DLL files - the product of your compiled strategy development. If doing just that didn't help, go to AppData and rename the Strategies folder so that Wealth-Lab won't find and load them at startup.

QUOTE:
This does NOT affect my data/strategy etc. as they are in appdata folder?

We don't need it currently, but no, it does not for the reason above.
profile picture

bobydesi123

#5
Hi Eugene,
I made changes as u had suggested. Removed my DLLs, PDB etc.
1. HOWEVER, if I rename the "Strategies" folder as u had suggested, the WLP DOES NOT load. I had to create an empty folder with name "Strategies".
2. Cleaned my registry.
3. Also disabled "check for updates" in extention manager, just in case.
Result:
Still takes about the same time to load, approximately 25-30 seconds.
The closing of program seem to work fine now! No warning/error messages by vista.
One more thing, I have dataset with 3000 symbols in daily scale, 125 1min and 125 5min data.
What is normal loading time? I only run IE,Active trader Pro, WL5, VS2008 and MATLAB occasionally. Have quad pro, with 6gb of RAM, SSD.
profile picture

Eugene

#6
Re: Extension Manager update check - good idea, but it works in a separate thread and therefore shouldn't block WLP from loading.

A couple more suggestions:

* For hints, try checking the Logs\Log.txt file under AppData (next to the Data folder), paying attention to the lines marked with the time when WLP started.
* Try renaming the entire Data\WealthLabPro folder (e.g. to WealthLabProX) and starting WLP.
profile picture

bobydesi123

#7
Eugene,
* Try renaming the entire Data\WealthLabPro folder (e.g. to WealthLabProX) and starting WLP.
Vista WILL NOT let me rename the folder, i am logged in as admin. Any suggestion?

Looked at log file, following is a snapshot of what seem to occur frequently. I had 2 or 3 WS open with 2 charts each running the same scrips and streaming different symbol with 1min, 5min scale.

Also, this time when I had closed WLP it received the error/warning message again from vista
Data Execution Prevention (DEP) closed the program......

Following is from log file.
1)
2010-02-13 20:59:26,375 [13] ERROR WealthLab.DataProviders.FidelityStreamingProvider [(null)] - 116: CStreamer::TranslateSymbol CustomRequest::NamedRequest failed
2010-02-13 20:59:26,375 [1] ERROR d0 [(null)] - 106: CStreamer::Unsubscribe TranslateSymbol Failed
2010-02-13 20:59:26,376 [26] ERROR WealthLab.DataProviders.FidelityStreamingProvider [(null)] - 106: CStreamer::Unsubscribe TranslateSymbol Failed
2010-02-13 20:59:26,520 [1] ERROR d0 [(null)] - 91: CStreamer::Subscribe Not Authenticated
2010-02-13 20:59:26,520 [13] ERROR WealthLab.DataProviders.FidelityStreamingProvider [(null)] - 91: CStreamer::Subscribe Not Authenticated
2010-02-13 20:59:54,375 [1] ERROR d0 [(null)] - 116: CStreamer::TranslateSymbol CustomRequest::NamedRequest failed
2)
2010-02-16 12:59:48,080 [1] ERROR WealthLabPro.ChartForm [(null)] - Overflow error.
2010-02-16 15:19:38,830 [19] ERROR WealthLab.DataProviders.FidelityStreamingProvider [(null)] - 10: Change in tick lag.
2010-02-16 15:19:38,830 [1] ERROR d0 [(null)] - 10: Change in tick lag.
2010-02-16 15:29:57,088 [1] ERROR WealthLabPro.ChartForm [(null)] - Collection was modified; enumeration operation may not execute.
2010-02-16 15:34:07,905 [1] ERROR WealthLabPro.ChartForm [(null)] - Collection was modified; enumeration operation may not execute.

profile picture

Eugene

#8
QUOTE:
Vista WILL NOT let me rename the folder, i am logged in as admin. Any suggestion?

Shut WLP down before doing that, of course. Still no go - log off from Windows and log back in.
QUOTE:
Data Execution Prevention (DEP) closed the program

Solution: Data Execution Protection (DEP) messages

Is there a default workspace loading on startup? If yes, have you already tried to temporarily remove the default workspace?
profile picture

bobydesi123

#9
Eugene,
I managed to change folder name as u had suggested, restarted WLP.
Only difference was the WLP loaded with HOME page and a trade ticket. Still takes about the same time as before to load.
Followed ur link for DEP message, i guess, i will have to log out of Fidelity before i close WLP. This probably explains why I was NOT getting the DEP error all the time.

Also, just for comparing, i downloaded WLD-64 from website, installed and ran it. I received a messagebox "multi quote server not yet installed" etc. I hit "ok". and WLD FIRES UP FAST, may be 3-5 seconds INCLUDING closing of the messageBox. I know that WLD is a 64bit program and has only the default datasets(WL100 DOW etc) that it comes with but it is an order or more magnitude faster than the WLP.
and btw, thanks for ur attention and help.
profile picture

Eugene

#10
Thanks, understood.

So, we're back to point 3. Remove all the 3rd party DLLs but - especially, MultiQuoteServer's. (btw I'm not sure if Mtiqs loads in WLD x64 - is provider extension seen there?)
profile picture

bobydesi123

#11
Eugene,
I have changed the WLP folder so that WLP loaded only with the default datasets and strategy. So I guess we can rule out any problem with dataset and strategy.
I have deleted all the "other" DLLs, still loads slowly. In ur experience what should be the loading time for WLP on system that i have, quad pro, intel SSD, 1300mhz 6gb RAM? I do not remember WLP load time bothering me before, started noticing this in last 2-4 weeks, not sure of the time frame.
One more thing, I received DEP error again after closing WLP, I had logged out of Fidelity and turned off streaming before closing.
Following is more information about my WLP.


Addins:
Fidelity supported : WL HeatMap 1.0.0.0, EPVisualizer 2009.12
Other: Commmunity Components Library 2009.12
Provider:
Fidelity supported :Ascii Files Static 1.2.9.0,MSN static 1.2.3.0,WL4 Static 1.2.4.0,Yhoo 1.3.11.0
Other:None
Strategy:
Fidelity supported :
Other: none
Indicators:
Fidelity supported :TASC 2009.12.0.0
Provider:community 2010.01

The following are the list of ONLY DLLs that are NOT from either WL or fidelity.

(all other DLLs)
Interop.METALIBLib.dll
TreeMaps.dll
TeeChart.dll
Qwhale.*.dll
TIBSCO.EMS.dll
BlowFishNET.dll
log4net
Metalib
ControlLibrary
SyntaxSettingConverter
RequestManager
ZedGraph
CommunityComponenent.dll
CommunityIndicators.dll
MetaStockProvider

profile picture

Eugene

#12
Re: DEP - turn DEP off in Windows/BIOS.
QUOTE:
(all other DLLs)

TreeMaps.dll is a part of Heat Map Visualizer; ZedGraph.dll, Community.Componenents.dll, Community.Indicators.dll belong to the Community extensions. All the other DLLs are not "other", but built-in and some of them are crucial. All these files are OK, so please move them back.

My primary concern was your own DLLs and possible usage of COM interop (frequently causes those pesky c0000005 errors in mscorwks.dll, see my message from 2/16/2010 3:57 AM - this is not a WLP-induced error) either in your code or in Mtiqs provider.

I consider starting in under 20 seconds to be acceptable on slower machines for a stuffed installation (e.g. a thousand Strategies, heaps of data and mostly all the available extensions).

I have nothing else to suggest but to temporarily start with clean environment: without %AppData%\WealthLabPro, without any community and 3rd party DLLs, with any sort of antiviral/firewall software turned off, DEP disabled, having WLP installation repaired from Control Panel (don't think it makes a lot of sense to repair .NET installation since WLD5 starts like a rocket).
profile picture

bobydesi123

#13
Eugene,
May be I was not clear in my last post. The "other" DLLs that i had mentioned are still under WLP5 folder, i did NOT remove them, I was just stating that those were("other") DLLs i had under WLP besides the obvious ones with the names fidelity or WealthLab in their DLL names.

I consider starting in under 20 seconds to be acceptable on slower machines for a stuffed installation (e.g. a thousand Strategies, heaps of data and mostly all the available extensions).
- I dont have that many strategies
- As I had mentioned before, have 2K symbols in daily, 125 in 1min and 125 in 5min. scale
-Just have vs2008,MS office, MATLIb as my other applications besides, WLP and ActivePro from fidelity.

-My WLP loads in just about 20-25 seconds, and my system i believe is pretty good with SSD and 1333mhz ram.
I wish I can find solution to this. Is unstall and re-install of WLP a good idea? Do I have to backup all my stategy/data before i do it?
Anyways, thanks for ur help.
profile picture

Eugene

#14
QUOTE:
Is unstall and re-install of WLP a good idea? Do I have to backup all my stategy/data before i do it?

Backup the entire %AppData%\WealthLabPro and then rename, uninstall WLP, remove any file that's left, install it fresh. If still no luck - the reason is somewhere outside of WLP.
profile picture

Eugene

#15
Have you tried my last suggestion?
profile picture

bobydesi123

#16
Eugene,
Sorry, I have not tried ur suggestion yet but will do it and post it here.
profile picture

bobydesi123

#17
Eugene,
Sorry i was busy and late to respond. I did try ur suggestion on 4/5/2010. I did not help. I also unistalled the WLP, down loaded it back from fidelity and re-installed the WLP. Still the same problem. I even tried with having only one dataset of daily NDX100 after the fresh install of WLP.
As I had mentioned previously the trial copy of WLD64 loaded up in a flash. Thank for all ur help..i guess i am NOT going to worry about it. May be WLP64 might do the trick when released in summer.
It is only an issue when i use vs2008 to debug WLP code and having VS start the WLP specially when i have some dll that are referenced by both the VS and WLP. May be i should have exact replicas of all DLL one for VS2008 and other for WLP.
profile picture

Eugene

#18
QUOTE:
It is only an issue when i use vs2008 to debug WLP code and having VS start the WLP specially when i have some dll that are referenced by both the VS and WLP.

Please tell me this ain't some kidding?

After I repeatedly stressed the fact that any 3rd party DLLs (including yours) should be removed from WLP's main folder, we're made aware of this petite, insignificant fact three months later?

If you haven't contacted Microsoft regarding slow VS2008 start in Debug mode (after all, Visual Studio isn't a Fidelity product), hope this helps to close this question:

Slow debugging issue in Visual Studio

P.S. Applications always start slower in debug mode.
profile picture

bobydesi123

#19
Eugene,
"After I repeatedly stressed the fact that any 3rd party DLLs (including yours) should be removed from WLP's main folder, we're made aware of this petite, insignificant fact three months later?"
May be i wasnt clear.
I went through that months before..also renaming the WLP folder and every suggestion u had made under the sun.
Problem with VS and WLP is different issue.
But in any case as i had mentioned in my last post.. i am NOT going to worry about it. As always u have been great help! Thxs.
profile picture

Eugene

#20
QUOTE:
Problem with VS and WLP is different issue.

When you debug in VS, you typically set output folder to WLP's main folder. Where VS will place the compiled library and symbol files.
profile picture

bobydesi123

#21
Eugene,
QUOTE:
When you debug in VS, you typically set output folder to WLP's main folder. Where VS will place the compiled library and symbol files.

Answer is YES.
For many days i was able to have VS write to WLP folder. Debug strategy and if buggy go back to VS make changes and debug strategy again without VS complaining "Access denied" , hence keeping the WLP running and no need to restrat WLP. Then, something happened, probably made a refernce to some dll or something, dont know. Now i cant do it anymore. Every time i have to shut down WLP and then VS can write to the WLP folder.
I am right now writing my own utility DLL, even if i have VS save it to poject folder and then manually try to copy DLL to the WLP folder i cant do it (access denied etc.) while WLP is runnig, but has a blank WS, i.e. no strategy opened. I guess WLP is some how referencing my DLL even when there are no strategy running. Yes, i am running in admin mode.
Thxs.
profile picture

Eugene

#22
QUOTE:
Every time i have to shut down WLP and then VS can write to the WLP folder.

You didn't do anything wrong. It's simply impossible to overwrite a compiled Strategy DLL, even with elevated privileges (as admin), because WLP loads Strategies and Strategy libraries at startup.

Same thing with copying a Strategy's XML file in Explorer while WLP is open - WLP won't notice the new one until you close and restart it.
profile picture

bobydesi123

#23
Eugene,
Thxs for clearing that up.