CTI indicator issues: hang, exception, crash

Author: maximgl

Creation Date: 7/29/2018 7:35 PM

Wealth Lab » Technical Indicators » CTI indicator issues: hang, exception, crash

maximgl

7/29/2018 7:35 PM

Hello,

I am observing strange (and seemingly reproducible) issue with CTI indicator. Following steps reproduce the issue on my machine:

1. Open WealthLab.
2. Open New SPY chart, data range from 1/1/2017 to 7/20/2018
3. Open Indicators Panel -> Community Indicators and drag CTI indicator onto SPY
4. Use default settings: Bars: SPY, Data Series: Close, Period 20, Positive Only: Unchecked.
5. Click OK button.

This sequence usually produces one of 2 outcomes:
1. The indicator is not added. In this case, re-adding the indicator again seems to be working fine.
2. WealthLab hangs with high CPU utilization. I've waited for some time, but it seems that the only way to get out of this state is to kill the app.

If I change one parameter in step 4, (select Positive Only checkbox), I can get 3rd outcome - Unhandled exception message:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AggregateException: One or more errors occurred. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at WealthLab.DataSeries.op_RightShift(DataSeries ds1, Int32 value)
at Community.Indicators.LNRet..ctor(Bars bars, DataSeries ds, Int32 period, String description)
at Community.Indicators.LNRet.Series(Bars bars, DataSeries ds, Int32 period)

Interestingly, clicking on Continue button and re-adding same indicator again (with "positive Only" enabled) seems to be working fine.

I have 2018.05 version of Community Indicators library.

Did anyone else experience this?

Size:

Color:

Hello,

I am observing strange (and seemingly reproducible) issue with CTI indicator. Following steps reproduce the issue on my machine:

1. Open WealthLab.
2. Open New SPY chart, data range from 1/1/2017 to 7/20/2018
3. Open Indicators Panel -> Community Indicators and drag CTI indicator onto SPY
4. Use default settings: Bars: SPY, Data Series: Close, Period 20, Positive Only: Unchecked.
5. Click OK button.

This sequence usually produces one of 2 outcomes:
1. The indicator is not added. In this case, re-adding the indicator again seems to be working fine.
2. WealthLab hangs with high CPU utilization. I've waited for some time, but it seems that the only way to get out of this state is to kill the app.

If I change one parameter in step 4, (select Positive Only checkbox), I can get 3rd outcome - Unhandled exception message:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AggregateException: One or more errors occurred. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at WealthLab.DataSeries.op_RightShift(DataSeries ds1, Int32 value)
   at Community.Indicators.LNRet..ctor(Bars bars, DataSeries ds, Int32 period, String description)
   at Community.Indicators.LNRet.Series(Bars bars, DataSeries ds, Int32 period)

Interestingly, clicking on Continue button and re-adding same indicator again (with "positive Only" enabled) seems to be working fine.

I have 2018.05 version of Community Indicators library.

Did anyone else experience this?

Eugene

7/29/2018 8:38 PM

Hi Maxim,

I just wondering if you're running WLP with debugger attached? I cannot reproduce the issue in WL 64-bit unless I do so myself. (Or it may be how your Windows is configured.)

Eugene

7/30/2018 5:04 AM

Oddly enough, the behavior is different in 32-bit WL (I work with 64-bit WL). CTI can even crash it. Weird.

The issue supposedly has to do with the LNRet indicator parallelization inside the CTI.

Thanks for the heads-up.

maximgl

7/30/2018 5:37 AM

Hi, I was not running WLP with debugger and I was actually using 64 bit version (6.9.19.0 64-bit Edition Build 1), but I am glad you were able to reproduce it on 32 bit version - I hope if there is ever a fix for 32 bit, it might fix it for my 64 bit version as well.

Thanks,
Maxim