Hi Venu;

  The crash is within the "DW Expression Evaluator" module. So that could be a computed column, expression on a column/ band, expression on a property, etc that is somehow crashing the DWO at runtime. Any recent changes to that DWO?

  Have you tried ...

1) Regenerating the faulting DWO / Child DWOs?

2) Optimizing your PBLs?

3) Performing an App full build - checking for compile errors or warnings?

Regards ... Chris

Thanks for your Response Chris.

There is no recent changes DWO.

1) Regenerating the faulting DWO / Child DWOs?

      Yes Regeneration done all the PBL's and no error.

2) Optimizing your PBLs?

     PBLs are already optimized and all are in sync.

3) Performing an App full build - checking for compile errors or warnings?

     Done Full build no compilation error.

Additional info.

 "Opentab" function success for 3 times, at 4th instance system preform the opentab it's getting crashed. 

Opentab operation performed in FOR loop.

Regards,

Venu

Try disabling accessibility if your app doesn’t need to use it:  https://www.appeon.com/developers/get-help/knowledgebase/negative-impact-accessibility-application-performance.html

On a "is it plugged in?" level:


Step through your application one line at a time in that loop where the crash eventually occurs.

Since you KNOW it will crash on the 4th iteration of the loop, and you know it will crash on the OpenTab command, stop RIGHT THERE in debug mode, and look at ALL o f the objects involved. Check everything you can to see if you can identify the anomoly causing the crash. It's amazing how often doing this will identify the issue.