Questions? Feedback?powered byOlark live chat software
Bug 3607

App crash with no error message 09 December, 2019

Prasanth Kalivarapu
11 November, 2019
Product: PowerBuilder Category: PowerScript IDE
Version: 2019 Publishing: Public
Status: Analyzing Priority: P2
Classification: Resolution:
Ken Guo 09 December, 2019
Hi Prasanth,

I got it. Thanks!

Regards,
Ken
Prasanth Kalivarapu 09 December, 2019
Hi Ken

Steps to load application:

Select application --> browse to appcrash.pbl --> select the application beneath it.
Open Library list which shows different objects. You can run the application.

Note: Please copy all respective C++ dlls provided with PB2019 appcrash issue.

Please provide meeting link if you still have any issue to discuss further.

Thanks
Prasanth
Ken Guo 09 December, 2019
Hi Prasanth,

Due to that we don’t have PB 7 on our side, our minimum version is PB 8. 
I used PB 8/9/10/11.5/12.6/2017 separately but can’t open your PB 7 PBL file directly. I also tried the method New > Existing Application but still not luck.

Could you please provide a complete case with PBT? Or could you please upgrade it to PB 8 or PB 9 first and then send the PBT and PBL for us?


Regards,
Ken
Prasanth Kalivarapu 09 December, 2019
appcrash.pbl (277KB)

Hi Ken,

I have attached PB7 dll as discussed. 

Thanks
Prasanth
Ken Guo 08 December, 2019
Hi Prasanth,

Sorry for the late reply.
Our developers are still analyzing this issue. Could you please provide a PB7 test case for us so that we could make a contrastive analysis? Due to that you mentioned it works well in PB7, we will upgrade the PB7 test case to other versions and analyze it gradually.


Regards,
Ken
Prasanth Kalivarapu 02 December, 2019
Hi Ken

Looking for an update, since it is a major roadblock for us to proceed further. 
Can you please let me know what can be done to proceed further?

Thanks for your help.

Thanks
Prasanth
Ken Guo 22 November, 2019
Hi Prasanth,

Currently we haven’t made any progress yet. We will let you know here once there is any updates.

Regards,
Ken
Prasanth Kalivarapu 21 November, 2019
Hi Ken

Thanks Ken, Please let me know any updates on this issue.
Note: we didn't had any issues as such in PB7. When we migrated to PB2019, we are experiencing this application crash issue.

Thanks
Prasanth
Ken Guo 20 November, 2019
Hi Prasanth,

I'm working on analyzing your case. I will keep you posted of the results here.

Regards,
Ken
Chris Pollach 19 November, 2019
Hi Prasanth;

  Thank you for those extra DLL's. I was able to recreate your App Crash on a mouse click on the User Object. In the O/S event log, I then saw ...

-----------------------------------------------------------------------
Faulting application name: ticket3607.exe, version: 1.0.0.1, time stamp: 0x5ce82bed
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xffff067d
Faulting process id: 0x42ac
Faulting application start time: 0x01d59f03a04a1e3a
Faulting application path: C:\Dev\PB2019\Bugs\GA\3607\ticket3607.exe
Faulting module path: unknown
Report Id: db13dc06-c09e-4d4f-a4aa-5bde17c9a121
Faulting package full name: 
Faulting package-relative application ID: 
-----------------------------------------------------------------------

   I also tried a /PBDEBUG as well but that did not seem to capture where or why the App crashes at the click event.

   I will now pass this ticket over to the main Support / Engineering team for their review of this crash issue.

Regards ... Chris
Prasanth Kalivarapu 19 November, 2019
required_dlls.zip (546KB)

Hi Chris 

I have attached all the required Supported dlls. Hope this works.

Thanks
Prasanth
Chris Pollach 19 November, 2019
Hi Prasanth;

  Thank you for the missing DLL. 

  However, even with the DLL in the same folder as the App. The error persists (see attached). I suspect that there are other files missing and/or special O/S registration(s) required, license file, etc in order for the OCX to work properly. Thus, I cannot replicate your issue currently.

Regards ... Chris
Chris Pollach 19 November, 2019
Test by Chris (Missing DLL)
Prasanth Kalivarapu 19 November, 2019
mpegraph.dll (376KB)

Hi Chris

I am attaching then dll used below. Can you please help me with the issue?
If there are some issues replicating the issue then lets schedule a call to go over with it.

Thanks
Prasanth
Chris Pollach 18 November, 2019
Hi Prasanth;
  
   Thank you for the Test Case!

   Unfortunately, your PB App requires an OCX and stops immediately upon launch looking for the "mpegragh.dll" in line #2 of the Constructor event of the "u_graphic_canvas" object class.

   Unless you can supply the missing 3rd party control and its run-time DLL(s), it will be hard to diagnose your problem any further.

Regards ... Chris
Prasanth Kalivarapu 18 November, 2019
test.pbl (647KB)

Hi Chris

We have created a sample application which has same behavior of app crash.
Steps to recreate:
1. Run test application.
2. Click on the embedded user object. App crashes.
Chris Pollach 13 November, 2019
Hi Prasanth;

  My suggestions at this time would be ...

For ... 

#1: Use the PB Debugger and try to step through your PowerScript code in the area where the app most crashes.

#2: Note that PB2019 is not certified for O18C. This will be coming in PB2019R2 due out Q1 of 2020.

#5: Have you done this?

#7: Note that external O/S Unicode functions have the letter W in the name. 
For example ...

ANSI: FUNCTION uLong FindWindow ( ref String classname, ref string windowname ) Library "USER32.DLL" ALIAS FOR "FindWindowA;ansi"

Unicode: FUNCTION uLong FindWindow ( ref String classname, ref string windowname ) Library "USER32.DLL" ALIAS FOR "FindWindowW"

Note1: The Unicode external function declaration format is the preferred one.
Note2: Progra_pack is only required when passing structures.

#10: Does your app seem to crash when Window's have these external controls defined on them?

#12: Have you checked with your 3rd party vendor for updated DLL's that are W10 compliant?


OTHER suggestions ...

a) In the PB IDE's "System Options" dialog, turn on (enable) "Enable PBDebug Tracing".
b) In your App's Oracle connection, start SQL Tracing ...
   ie:  SQLCA.DBMS = "TRACE ORA"

Regards ... Chris
Prasanth Kalivarapu 13 November, 2019
Hi Chris
  Can you tell us ...

1) Is this when running the App from the PB IDE?  YES
2) Are you connecting to O12CR2 via the native driver (ORA)? Now we have been using Oracle 18c 
3) Do you use the Full Oracle client or just the "Instant Client"? Full Oracle client
4) Does the App always crash in the same area (process)? YES
5) If the answer to #1 is YES... Have you tried optimizing all your PBL's
and then performing a FULL Build?
6) When you migrated from PB7 - did you run the PB2019 "Migration Assistant"
against the PB7 code first? YES -- Some basic keywords such as selected is shown more.
7) PB 7 was ANSI based whereas PB10 and higher versions are Unicode. Did you
refactor your PowerScript to be Unicode compliant. Yes -- Did by appending alias for "<function name>;Ansi" progma_pack(1) in local external functions
8) Does your PB App use any O/S API calls? If so, were any of these commands
converted to be Unicode compliant? What exactly do i need to do in order to make it unicode compliant
9) Does your App use the PFC? If so, did you download the latest PFC version
that matches the PB Version? No. But will try downloading them and appending to the list
FYI:  https://github.com/OpenSourcePFCLibraries
10) Does your PB App use any external controls? Yes
11) Does your PB App use any OLE connections? 
12) Does your PB App use any 3rd party DLL's? Yes // C++ dll's to make them compliant added alias for "<function name>;Ansi" progma_pack(1) in local external functions

Regards ... Prasanth
Chris Pollach 11 November, 2019
Hi Prasanth;

  Can you tell us ...

1) Is this when running the App from the PB IDE?
2) Are you connecting to O12CR2 via the native driver (ORA)?
3) Do you use the Full Oracle client or just the "Instant Client"?
4) Does the App always crash in the same area (process)?
5) If the answer to #1 is YES... Have you tried optimizing all your PBL's and then performing a FULL Build?
6) When you migrated from PB7 - did you run the PB2019 "Migration Assistant" against the PB7 code first?
7) PB 7 was ANSI based whereas PB10 and higher versions are Unicode. Did you refactor your PowerScript to be Unicode compliant.
8) Does your PB App use any O/S API calls? If so, were any of these commands converted to be Unicode compliant?
9) Does your App use the PFC? If so, did you download the latest PFC version that matches the PB Version?
FYI:  https://github.com/OpenSourcePFCLibraries
10) Does your PB App use any external controls?
11) Does your PB App use any OLE connections?
12) Does your PB App use any 3rd party DLL's?

Regards ... Chris
Prasanth Kalivarapu 11 November, 2019
*Phenomenon:
App crashes with no error message.
Recently we have migrated our application from PB7 to Appeon PB2019. 

Snapshot from event viewer
Faulting application name: PB190.EXE, version: 19.0.0.2082, time stamp: 0x5ce82c5c
Faulting module name: PBVM190.dll, version: 19.0.0.2082, time stamp: 0x5ce82deb
Exception code: 0xc0000005
Fault offset: 0x001f4216
Faulting process id: 0x4644
Faulting application start time: 0x01d5984e2593bd17
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.EXE
Faulting module path: C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBVM190.dll
Report Id: c31f5d0d-1fab-4a2f-9a5f-b7cd5a7c7c89
Faulting package full name: 


*Reproduce Steps:
Application is crashed with no error message in some screens.


Remarks:
OS:
Windows 10 
Platform:
32-bit 
Database Type:
Oracle 
Database Version:
12CR2