• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Application Terminated/crashed Without any message - PB2019

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Application Terminated/crashed Without any message - PB2019

  1. Issue
0
Votes
Undo
  1. Venugopal r
    Venugopal r
  2. PowerBuilder
  3. Wednesday, 14 September 2022 19:21 PM UTC

Hi Team,

Greetings!

We are usingĀ 2019 - Build version 2170.

Application Terminated/crashed certain cases without any error. Trace and debug also not pointing the exact issue location.

However I checked in the event viewer below is the reason for application termination.

We thought this is due to memory issue , hence we build .exe in 64-bit and tried the same but no luck, still same issue.

Exactly our code does dynamicallyĀ creatingĀ multipleĀ tabs using "OpenTabWithParm" function and assigning DW & retrieving it.

Any suggestion to avoid this issue. If any more information required please let me know I will add it.

Thanks in advance

Regards,

Venu.

PowerBuilder 2021 display WebView2 controller
Job Opportunity - California
Responses (4)
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 15 September 2022 13:35 PM UTC
  2. PowerBuilder
  3. # 1

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.

Comment
Venugopal r
  1. Venugopal r
  2. Thursday, 15 September 2022 13:42 PM UTC
Thanks For your Response Olan.

Today I did exactly what you suggest, but the application crashing some time in 4th iteration another time it crash 10th iteration. So we can't predict the exact loop number.

Also, during the crash I unable to stop the command in Opentab , since as soon as it's reached to that command suddenly application crashed.
  1. Helpful
Olan Knight
  1. Olan Knight
  2. Thursday, 15 September 2022 13:53 PM UTC
That was the right thing to try.

Have you tried applying the 4GB_PATCH to your 32 bit executable?

https://ntcore.com/?page_id=371



We started using this and it resolved all of our memory issues.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 14 September 2022 22:43 PM UTC
  2. PowerBuilder
  3. # 2

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

Comment
There are no comments made yet.
Venugopal r
Venugopal r Accepted Answer Pending Moderation
  1. Wednesday, 14 September 2022 20:43 PM UTC
  2. PowerBuilder
  3. # 3

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

Ā 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 14 September 2022 21:36 PM UTC
Hi Venu;

Thank you for the feedback!

I would now suggest though opening up a Support Ticket. for this issue! :-(

Regards ... Chris
  1. Helpful
Venugopal r
  1. Venugopal r
  2. Thursday, 15 September 2022 06:43 AM UTC
Sure Chris. Let me raise a ticket.

Would you kindly assist me in determining whether there is any memory improvement between 32-bit and 64-bit exe, particularly the action during the TAB, DW assign / open in run time?



Thanks,

Venu
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 15 September 2022 15:23 PM UTC
Hi Venu;

Yes, the App's O/S's "Address Space" (work area) in 64 bit mode is HUGE compared to a 32 bit App EXE. ;-)

Regards ... Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 14 September 2022 20:33 PM UTC
  2. PowerBuilder
  3. # 4

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

Ā 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.