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

Resolved PB Runtime Crash

  1. Issue
0
Votes
Undo
  1. David Peace (Powersoft)
    David Peace (Powersoft)
  2. PowerBuilder
  3. Tuesday, 3 May 2022 16:28 PM UTC

Hi Everyone

I have a PB App 2019R3 latest build and runtimes. It processes large amounts of data from an external OLE source and inserts/updates a SQL server database.

Randomly the PB runtime just disapears with no messages or anything. The Evenlog shows the following entries:

First a .Net Runtme error:

Application: PB190.exe
CoreCLR Version: 4.700.21.26205
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 726E336E

Then Application Error:

Faulting application name: PB190.exe, version: 19.2.0.2728, time stamp: 0x6100e4a4
Faulting module name: VCRUNTIME140.dll, version: 14.30.30704.0, time stamp: 0x615a9224
Exception code: 0xc0000005
Fault offset: 0x0000336e
Faulting process id: 0x40c8
Faulting application start time: 0x01d85f01736194f2
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 0d828f11-e7f2-4739-8e30-4a5fe1a2bee1
Faulting package full name:
Faulting package-relative application ID:

Then Windows Error reporting:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: PB190.exe
P2: 19.2.0.2728
P3: 6100e4a4
P4: VCRUNTIME140.dll
P5: 14.30.30704.0
P6: 615a9224
P7: c0000005
P8: 0000336e
P9:
P10:

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PB190.exe_5e548d90a58e8346511b86dbd9fa9b4a47f640fa_d4735fa1_e5f60df9-27cc-4f69-af1e-21de8c533102

Analysis symbol:
Rechecking for solution: 0
Report Id: 0d828f11-e7f2-4739-8e30-4a5fe1a2bee1
Report Status: 4
Hashed bucket:
Cab Guid: 0

-----------------------------------------------------------------------------------------------

Any thoughts? Before I raise a support ticket.

Thanks

David

 

  1. PowerBuilder
TabControl close tab page (summary of missing feat...
URGENT: Richt Text Edit Control
Accepted Answer
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Wednesday, 18 May 2022 13:49 PM UTC
  2. PowerBuilder
  3. # Permalink

Just to let you know that I managed to resolve this by adding garbage collection in the processing loop. Thanks for all your suggestions.

Comment
There are no comments made yet.
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 3 May 2022 16:49 PM UTC
  2. PowerBuilder
  3. # 1

Hi David;

   Looks like the main culprit could be the "VCRUNTIME140.dll" which is not from the PB realm. Since your app is using ole, I would make sure that the Error Event is coded on the OLE container & add a TRY..CATCH around the OKE processing to handle OLE exceptions. Also, if an Exception is caught, it could give you more diagnostics as to the actual problem if it is an OLE problem taking down the PB app. HTH

Regards... Chris 

Comment
Load more comments
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Wednesday, 4 May 2022 12:56 PM UTC
Yes, I found that too! We are using a .Net DLL for email but the job only emails for start & end. The ODD thing is that it seems to only crash when run from the IDE, in deployment it's fine (or so it seems)!



I do not like random crashes they always leave me nervous about the production running. I'll monitor this over a few days in our QA environment. If it doesn't crash there then I'll assume all will be well.

  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Wednesday, 4 May 2022 12:57 PM UTC
I forgot to say that the the .Net DLL is made using snap develop and is Core 3.1
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 4 May 2022 14:08 PM UTC
Hi David .. thanks for the additional feedback. Maybe the .NET Core DLL is still trying to complete some processing the odd time that leads to the crashing issue. I wonder if adding a YIELD() command after the .Net API call to process the email might help here to allow processing to complete before the PB App continues its PowerScript journey?
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 3 May 2022 19:43 PM UTC
  2. PowerBuilder
  3. # 2

Hi,

Probably not very helpful, but I've seen loads of "Exception code: 0xc0000005" when running PB.

For example see: https://www.stellarinfo.com/blog/how-to-fix-error-code-0xc0000005-in-windows/

Maybe the best thing is to create a ticket indeed,

regards,

MiguelL

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.