Bug 5414

issue with PBD creation 20 October, 2020

Sreerama Harikrishna
09 October, 2020
Product: PowerBuilder Category: PowerBuilder Runtime
Version: 2019 Build: 2170
Classification: Publishing: Public
Priority: P1
Status: Analyzing Reason:
Chris Pollach @Appeon 20 October, 2020
#12
Hi Sreerama;
 
  The next steps would be ...

1) provide a simple test case that reproduces the issue

2) run your application through the PB IDE debugger and locate the failing statement(s) if possible.

3) Execute your PB App EXE with a PB Trace to give us more information around the crash.  For example"

  <YourApp.exe>  /pbdebug 

   Please attach the trace file to this ticket.

Regards ... Chris
Sreerama Harikrishna 20 October, 2020
#11
Hi Chris,

we have executed exe with compatibility and Troubleshoot Compatibility options and then still i am facing the same issue.any other solution/workaround i can try?

@Miguel Leeuwe: we have not used any themes in our application.
Miguel Leeuwe 19 October, 2020
#10
Hi Sreerama,
Not sure if true, but I had a major crash the other day while trying to build a single PBD too. 
Are you using "Themes"? As a test: Can you try to temporarily deactivate the use of themes and do the single build again?
Sorry if it has nothing to do, but it's worth giving it a go.
regards and sorry for the interrupt
:)
Chris Pollach @Appeon 19 October, 2020
#9
Hi Sreerama;
 
  Thank you for he mini-dump. I see that the error is in the "PBSHR190" DLL. This module normally handles requests to the O/S on behalf of the PBVM. 

  Can you try using the MS-Windows "compatibilty" feature? Just use the RHMB on your PB App;s EXE and select the "Troubleshoot Comatibilty" option from the pop-up menu in W10 and see what it recommends?

Regards ... Chris
Sreerama Harikrishna 19 October, 2020
#8
Hi Chris

Not possible to provide application for your reference. is there any other suggestion i can try out. can you any thoughts by seeing below event log:

Event log:
Faulting application name: tbs.exe, version: 1.0.0.1, time stamp: 0x5e03ac98
Faulting module name: PBSHR190.dll, version: 19.0.0.2170, time stamp: 0x5e03ac9c
Exception code: 0x80000003
Fault offset: 0x00129250
Faulting process id: 0x31f4
Faulting application start time: 0x01d69e403066300e
Faulting application path: C:\tbs.exe
Faulting module path: C:\PBSHR190.dll
Report Id: f4c9efe9-1676-46a4-8d03-f639452d6a8e
Faulting package full name:
Faulting package-relative application ID:
Chris Pollach @Appeon 15 October, 2020
#7
Hi Sreerama;
 
  Thank you for confirming that this is a multi-developer issue.

  As soon was we have a test case, we can get Engineering involved to further diagnose this issue.  Many thanks in advance!

Regards ... Chris
Sreerama Harikrishna 15 October, 2020
#6
Hi Chris

Thanks for quick response. Yes other developers also getting same issue.i am in the process of creating test application for your reference.
Chris Pollach @Appeon 15 October, 2020
#5
Hi Sreerama;
 
  Thank you for testing the Full Optimize step to see if that cures your incremental build issue.

  I am not able to replicate your issue in mu PB 2019 build 2170 test applications.

  Would have a simple Test Case PB App that demonstrates this issue that you can attach to this ticket?

  Also, are other PB Developers having this issue?

Regards ... Chris
Sreerama Harikrishna 15 October, 2020
#4
Hi Chris

we have done optimize  for all pbl's and full build successfully done. again generated PBD via incremental build for required PBL's .while placing newly generated PBD in application folder then application is getting terminated.

Event log for above crash.

Faulting application name: tbs.exe, version: 1.0.0.1, time stamp: 0x5e03ac98
Faulting module name: PBSHR190.dll, version: 19.0.0.2170, time stamp: 0x5e03ac9c
Exception code: 0x80000003
Fault offset: 0x00129250
Faulting process id: 0x24ac
Faulting application start time: 0x01d6a2d57f7671c9
Faulting application path: C:\test\tbs.exe
Faulting module path: C:\test\PBSHR190.dll
Report Id: 0d00fe7d-a059-4537-9bfc-77f31a5bf909
Faulting package full name:
Faulting package-relative application ID:
Sreerama Harikrishna 09 October, 2020
#3
i am in the process of all PBLs optimization.
Sreerama Harikrishna 09 October, 2020
#2
i have done optimzer for one pbl and created PBD for the same. still i am getting crash( application terminating with out error). 
Event log:
Faulting application name: tbs.exe, version: 1.0.0.1, time stamp: 0x5e03ac98
Faulting module name: PBSHR190.dll, version: 19.0.0.2170, time stamp: 0x5e03ac9c
Exception code: 0x80000003
Fault offset: 0x00129250
Faulting process id: 0x31f4
Faulting application start time: 0x01d69e403066300e
Faulting application path: C:\tbs.exe
Faulting module path: C:\PBSHR190.dll
Report Id: f4c9efe9-1676-46a4-8d03-f639452d6a8e
Faulting package full name:
Faulting package-relative application ID:
Chris Pollach @Appeon 09 October, 2020
#1
Hi Sreerama;
 
 In searching the support database, I have not encountered any such issue in either PB 2017 Rx or PB 2019 Rx releases. 

  The most likely cause could be a corrupt object or a corrupt PBL that is causing this IDE crash. The first recommendation I would have would be to optimize all your PBL libraries within your application. After that, again perform a Full Build. Then try the PBD generation again.

Regards ... Chris
Sreerama Harikrishna 09 October, 2020
*Phenomenon:
While accessing a newly created PBD via incremental build, application is crashing (which contains all PBDS along with newly generated PBD and Exe). Generated only one PBD without generating all PBDs.
After generating FULL Build and copy all PBDS along with Exe application doesn't crash.

In PB7 we didn't faced this kind of issue, where we were able to successfully generate single PBD and replace in our application folder along with other PBDs. Whereas this is not working in PB2019.

our requirement is delivering problematic  PBD to the customer.
OS:
Windows 10
Platform:
All
Database Type:
Oracle
Database Version:
19c