Occasionally WL7 seems to randomly terminate itself. There are no error reports or exception notifications. It's happened on two seperate machines with wildy different specifications.
Is there a logfile I could review to help determin cause?
Termination has occured:
1) During Backtests
2) Optimizations
3) When looking through Backtest & Optimization results.
If anyone has some ideas please let me know.
Is there a logfile I could review to help determin cause?
Termination has occured:
1) During Backtests
2) Optimizations
3) When looking through Backtest & Optimization results.
If anyone has some ideas please let me know.
Rename
What about checking the Windows Log Viewer?
Based on Audit TImes I get the below one of the below errors. I'll clear my logs and see if I can catch the next instance.
and:
QUOTE:
The program WealthLab7.exe version 7.0.25.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 1850
Start Time: 01d7bcc275eaaa47
Termination Time: 12
Application Path: C:\Program Files\Quantacula, LLC\Wealth-Lab 7\WealthLab7.exe
Report Id: 24cb1336-fc2b-4a07-bdc0-4b6a9447d12c
Faulting package full name:
Faulting package-relative application ID:
Hang type: Unknown
and:
QUOTE:
Faulting application name: WealthLab7.exe, version: 7.0.28.0, time stamp: 0x5f3ed523
Faulting module name: coreclr.dll, version: 4.700.21.47003, time stamp: 0x6148c4e1
Exception code: 0xc00000fd
Fault offset: 0x000000000015bc48
Faulting process id: 0x28ec
Faulting application start time: 0x01d7c7d9cf1fa981
Faulting application path: C:\Program Files\Quantacula, LLC\Wealth-Lab 7\WealthLab7.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.20\coreclr.dll
Report Id: 4275ab40-4bb2-4564-8749-32312723dfc5
Faulting package full name:
Faulting package-relative application ID:
The first error speaks for itself, the program has stopped responding probably during a long running task and was closed. The second exception code suggests us that a stack overflow occurred.
I'm not sure what could be causing either of the two.
I only have my personal scorecard and WealthLab extensiions installed on the workstation that generated these reports. I'll check my code. But I'm not aware of anything that could be considered a "long running task". Caclulating the custom metrics takes only a a few seconds.
I'm not sure what the code in the coreclr.dll is running so I can't even begin to offer suggestions there.
I noticed an update (Build 29) today. I'll install that prior to further tests.
I only have my personal scorecard and WealthLab extensiions installed on the workstation that generated these reports. I'll check my code. But I'm not aware of anything that could be considered a "long running task". Caclulating the custom metrics takes only a a few seconds.
I'm not sure what the code in the coreclr.dll is running so I can't even begin to offer suggestions there.
I noticed an update (Build 29) today. I'll install that prior to further tests.
I've updated to [Build 29 and still getting this issue.
However it's no longer limited to backtest/optimization runs. There is a new windows Application Error in the Event log. This occurs when i try to access the preferences window. The program freezes then terminates. THe Preferences windows does nto get displayed. I've tested this multiple times on two different PC's.
Open WL7, click on Preferences shortcut button. The same occurs if trying to access the "metrics" preferences from an optimization tab.
I have also noticed a few times that the backtest will get stuck loading a datafile, then terminate after a while. Next time it happens I'll record as much data as I can.
However it's no longer limited to backtest/optimization runs. There is a new windows Application Error in the Event log. This occurs when i try to access the preferences window. The program freezes then terminates. THe Preferences windows does nto get displayed. I've tested this multiple times on two different PC's.
Open WL7, click on Preferences shortcut button. The same occurs if trying to access the "metrics" preferences from an optimization tab.
I have also noticed a few times that the backtest will get stuck loading a datafile, then terminate after a while. Next time it happens I'll record as much data as I can.
CODE:
Faulting application name: WealthLab7.exe, version: 7.0.29.0, time stamp: 0x5f3ed523 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc00000fd Fault offset: 0x00007ffad3ac27e1 Faulting process ID: 0x1eec Faulting application start time: 0x01d7d0bc974db5a1 Faulting application path: C:\Program Files\Quantacula, LLC\Wealth-Lab 7\WealthLab7.exe Faulting module path: unknown Report ID: 7f55b814-19bd-4e42-b22f-fbfd5682528a Faulting package full name: Faulting package-relative application ID:
Have you added any custom Preference Pages via the API? Personally I've never experienced this issue so it'll be a bit harder to troubleshoot.
The fact that itt's happened on two separate machines with wildly different specifications makes us believe that your custom DLL(s) may play a role. Could you remove the files and retry?
Interesting, there seems to be a conflict between my customer scorecard (code unaltered for several weeks now) and the new Finantic scoreCard.
Either can be installed and prefference pages show, but if both are installed I encounter the Unexpected Termination issue when trying to access the prefferences window.
I'll run my card in debug mdoe and see if I can find the issue. However, I don;t think this is the cause of the previously encountered terminatinos as the Financtic card was not installled.
I'll keep digging. Thanks for the pointers.
--> Update:
I think I may have found the problem, though I am not sure why it is surfacing now or why its only an issue if the Finantic Card is also installed. I'll need to test thoroughly to confirm.
Either can be installed and prefference pages show, but if both are installed I encounter the Unexpected Termination issue when trying to access the prefferences window.
I'll run my card in debug mdoe and see if I can find the issue. However, I don;t think this is the cause of the previously encountered terminatinos as the Financtic card was not installled.
I'll keep digging. Thanks for the pointers.
--> Update:
I think I may have found the problem, though I am not sure why it is surfacing now or why its only an issue if the Finantic Card is also installed. I'll need to test thoroughly to confirm.
ok, after a week away I've finally got back to investigating my custom scorecard. There seem to be several issues which are the most likely causes of these unexpected shutdowns.
Since making appropriate changes I have been running a 16hour optimization without error or shutdown. Fingers crossed that's the last I see of them.
Big thanks to Eugene and Glitch for their patience and support.
I'll share what I found below for others who may encounter similar issues and keep the post updated with any new issues i uncover.
Since making appropriate changes I have been running a 16hour optimization without error or shutdown. Fingers crossed that's the last I see of them.
Big thanks to Eugene and Glitch for their patience and support.
I'll share what I found below for others who may encounter similar issues and keep the post updated with any new issues i uncover.
QUOTE:
1) A number Extended ScoreCard metic names were changed as a result of the discussion on %-Based Outliers. My code was still referencing the old metric names in the reportHost method resulting in a "cannot convert Null to Double" error. References in my code have now been updated.
2) My error logging was not compensating for multiple threads (an issue for optimizations) resulting in a file exception if two or more threads tried to write to the error log at the same time. Considering the previously noted issue, this was frequent!
3) There were occasions when several Metrics were being refernced before populated resulting in a recursive loop of initialization. This was due to a lack of my understanding of when the initialize sub was called by WL7. (This is most likely the "long running task" issue noted in the Window Log)
4) The Error log write routine was using the old VB FreeFile Function, which I now undestand manages a limited number of files. If the limit is exceeded a Stack Overflow exception results. This may have been the cause of those logged by Windows Application Log. I have changed this to an IO call instead.
5) I have included significantly more error catch/handling code. When this was originally written it was a quick and nasty test of the WL7 API to get an idea of what it is capable of. I'll probably restructure the code significantly over the next few weeks as I incorporate more custom metrics for optimizations.
Thanks for sharing your findings. Well, Wealth-Lab is potent at providing the power user enough rope to shoot himself in the foot. ;-)
Yes, a reminder to include error handling in everything! Thanks again
A quick update. Since making the above mentioned changes to my Scorecard I have not had any issues with Unexpected Termination. Looks like that was the cause.
Big thank you again to Glitch and Eugene for their time and patience on this one.
Big thank you again to Glitch and Eugene for their time and patience on this one.
Glad to see you've figured out the source of error!
Your Response
Post
Edit Post
Login is required