Bug 5285

Crash APP when write infos from one Window to other window with DW 22 October, 2020

Daniel Oralek
18 September, 2020
Product: PowerBuilder Category: DataWindow
Version: 2019 R2 Build: 2338
Classification: Publishing: Public
Priority: P3
Status: Reproducing Reason:
Daniel Oralek 22 October, 2020
#10
(In reply to armando herrera  @Appeon from comment #9)
Hi Daniel, 

Are you still facing this matter? 
Is there anything else we can do to keep helping?. 

Regards!
Hi, yes I am. Now I am trying update our PFC to new version. Regards
armando herrera @Appeon 16 October, 2020
#9
Hi Daniel, 

Are you still facing this matter? 
Is there anything else we can do to keep helping?. 

Regards!
Mark Lee @Appeon 30 September, 2020
#8
Hi Daniel,

Thanks for providing the crash dump files. 

1. Currently we can’t find out the cause of it from the dump file. In the Dump files, it shows in time.exe(1).1000.dmp that the assembly instruction at PBSHR190+12c9a0 in C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSHR190.DLL has caused an unknown exception (0xc000041d) on thread 0
 
2. And regarding the feedback from other customers, using the PFC version that is not compatible with the PB version will cause some unknown crashing issues and will make the PB application unstable so we suggest that you can upgrade your PFC Framework and try it again.
 
Please note that:
The PFC libraries are now "Open Source" since PB 10.0. They have been moved however in recent years over to GitHub. You can find the PFC Framework in the link below:
https://github.com/OpenSourcePFCLibraries 
 
3. Since this issue is difficult to reproduce, can you provide a VM for us to reproduce it?

Regards,
Mark Lee
Mark Lee @Appeon 24 September, 2020
#7
Hi Daniel,

Thanks for reporting this problem! 
We will be working on analyzing your case. We will keep you posted on the results here.

Regards,
Mark Lee
Chris Pollach @Appeon 22 September, 2020
#6
Hi Daniel;

  Thank you for the crash dump files and the information on your current PFC version.

  I suspect that it's due to the handling of the PSR file(s). Since the crashes are random though, its hard to say.

  I will now transfer this ticket over to the main Support / Engineering team for their review of the dumps and their feedback on what might be causing this.

Regards ... Chris
Daniel Oralek 22 September, 2020
#5
CrashDumps.zip (799KB)

We did't update PFC only migrating from previous version. The DUMP is in attachment
Chris Pollach @Appeon 21 September, 2020
#4
  Thank you for those uploads!

  I see that your App is using the PFC framework. Out of curiosity, when you migrated to PB 2019 - did you refresh the PFC framework with the PB2019Rx version?

  When the App crashes ... do you get a MS-Windows App Event log entry? If so, please attach a copy of the mini-dump to this to ticket. 

Regards ... Chris
Daniel Oralek 21 September, 2020
#3
time.zip (242KB)

Hi Chris,
this problem happen in Development and Production too. I can do step but  IDE crash randomly in cyclus of loging of import. The PSR files are exported from APPEON PB but in source (in PBL) datawindow has header: release 11; It is after migration but normaly in application it is working. 
The pbdebug file is in attachment.
Chris Pollach @Appeon 18 September, 2020
#2
Hi Daniel;

  Thank you for the information from the MS-Windows event logs surrounding the application crash.

  Does this problem happen in the Development, Production or both? Have you been able to step through your App's code to the failure point using the IDE debugger? For EXE App execution tracing, have you tried using the "/PBDebug" option?

  Please note that PSR files are actually a copy of the DataWindow *Source* and its various buffer data. Due to that source code reliance on a PB version, a PSR produced in PB 11 is typically not compatible with PB 20xx (or PB 12.x for that matter) and vise versa. So you would need to refresh the PB 11.x PSR's in your DB with PB2019Rx equivalents. If not, random crashes may occur.

Regards ... Chris
Daniel Oralek 18 September, 2020
#1
Report.zip (5KB)

*Phenomenon:
In our application we have dialog using for import some PSR reports into database. Program code in NVO create row in table and then import PSR as blob into blob column. Result of this operation write into another Log window with DW. This log DW is simple dw with external data source only for loging. After importing few rows application crashes without any message - only write info into system application log. The detail information from Event Viewer of Application log is in attachment. Aplication crashes in PBSHR190.dll with exception 0xc000041d. 
When I stop writing result into log window it's finishing right. 

*Reproduce Steps:
I can reproduced it only on our application and i can't isolated error into some demo code. 

Remarks:
We migrating our app from PB11 where this code working well.
OS:
Windows 10
Platform:
32-bit
Database Type:
Microsoft SQL Server
Database Version:
MSSQL 2012