Bug 6016

After migrating to PB2019R3: OleCustomControl causing application crash 12 April, 2021

Tobias Roth
04 February, 2021
Product: PowerBuilder Category: PowerBuilder Runtime
Version: 2019 R3 Build: 2670
Classification: Publishing: Public
Priority: P3
Status: Analyzing Reason:
Communication Status: Waiting for Appeon
Ken Guo @Appeon 12 April, 2021
#21
Hi Tobias,

#1. We have not received similar feedback from other customers.
#2. Thanks for submitting this case! We will continue to analyze this issue and will keep you posted as soon as there is any progress.

Regards,
Ken
Tobias Roth 09 April, 2021
#20
Example_App.zip (384KB)

Hi Ken,

i have done further testing.
I have modified an existing example app with the following activeX OLE Controls: 
GDPicturePro5.GdViewer and rmpHTML.HTMLed (both ActiveX are registered on the provided VM)

Test: 
- Click one of the two Buttons 10 times and than close the opened windows fastly. And repeat it.
-> In PB2019R2 all works fine. No Crashes.
-> In PB2019R3 PB190 crashes with the following message:


Fehlerbucket 2210682633105081255, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: PB190.exe
P2: 19.2.0.2670
P3: 6009628d
P4: MSVBVM60.DLL
P5: 6.0.98.48
P6: 5ea8e7bc
P7: c000041d
P8: 0001a067
P9: 
P10: 

Name der fehlerhaften Anwendung: PB190.exe, Version: 19.2.0.2670, Zeitstempel: 0x6009628d
Name des fehlerhaften Moduls: MSVBVM60.DLL, Version: 6.0.98.48, Zeitstempel: 0x5ea8e7bc
Ausnahmecode: 0xc000041d
Fehleroffset: 0x0001a067
ID des fehlerhaften Prozesses: 0x14d4
Startzeit der fehlerhaften Anwendung: 0x01d72d535767f9c4
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.exe
Pfad des fehlerhaften Moduls: C:\Windows\System32\MSVBVM60.DLL
Berichtskennung: 23b5e8a1-65ad-4a61-9f9f-6c5aeadf8b50
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

Thanks
Regards Tobi
Tobias Roth 09 April, 2021
#19
Hi Ken,

do you have any other appeon custumers with the same problem?

Thanks
Regards Tobi
Ken Guo @Appeon 30 March, 2021
#18
Hi Tobias,

At present, we have not made progress on this issue, mainly because the DLL in this issue is a third-party DLL, and we do not have the source code of this aspect.


Regards,
Ken
Tobias Roth 29 March, 2021
#17
Hi Ken,

Are there any news?

Thanks and Regards, 
Tobi
Ken Guo @Appeon 05 March, 2021
#16
CrashReport

Hi Tobias,

After analyzing the dump file, we found that the crash happened in msvbvm60!Zombie_Release.
However, we are still not sure whether this crash is caused by the OLE control itself or PB at present.

Regards,
Ken
Tobias Roth 05 March, 2021
#15
Hi Ken,

are there any news?
Without a fix of this issue we can not migrate to PB2019R3.

Thanks

Regards,
Tobi
Tobias Roth 16 February, 2021
#12
Hi Ken,

unfortunately i have to correct my last message. 
The newly detected errors also have an OLE object on the window.

Regards,
Tobi
Tobias Roth 15 February, 2021
#11
Hi Ken,

we have detected other crashes with the same error message msvbvm60.dll.
I'll email you some other test cases tomorrow. The test cases do not contain any OLE objects.

The msvbvm60.dll new errors are also only in PB2019R3, not in PB2019R2. (exactly same sourcecode; just migrated + fullbuild)

Regards,
Tobi
Ken Guo @Appeon 09 February, 2021
#10
Hi Tobias,

I have used my account to log into PB IDE. I will keep you posted on the progress.
Note: We are going to have a holiday starting from Feb.11th to Feb.17th and will be back on Feb.18th. So this issue might be postponed. 
Appreciate your understanding.

Regards,
Ken
Tobias Roth 08 February, 2021
#9
Hi Ken,

download link is deactivated now.
I forgot to logout in the IDE (Auto Login activated). Please log in with your credentials when you start analyszing.

Thanks

Regards,
Tobi
Ken Guo @Appeon 08 February, 2021
#8
Hi Tobias,

We have downloaded the VM files, we will work on analyzing your case. I will keep you posted of the results here.

Regards,
Ken
Tobias Roth 05 February, 2021
#7
Hi Ken,

i have mailed the download link with the vhdx-file and the test case information to ken.guo@appeon.com.

Thanks,
Regards Tobi
Tobias Roth 05 February, 2021
#6
Hi,
we will provide you a vhdx-file auf partion c including windows 10 64bit. (hyper-v: generation 1 )
I will create the vm now and send the download link to ken.guo@appeon.com

Regards, 
Tobi
Ken Guo @Appeon 05 February, 2021
#5
Hi Tobias,

If you can provide us with a virtual machine, it is also a very good choice.
Please give us the download link of your virtual machine.

Regards,
Ken
Tobias Roth 05 February, 2021
#4
Hi Ken,

1. All worked well in the previous version (PB 2019 R2)
2. I already greated a small testcase, but all worked fine in it. The two processes have a lot dependencies to other objects.
Is it possible to install our product, production workspace with database/OCXs on a virtual machine on your side? In that way you can use every debug tool you want, without remote access.
Alternatively we can provide you the entire virtual machine as a download link. We are using Hyper-V-Manager. 
I think providing the virtual machine as download link would be easier.

Regards,
Tobi
Ken Guo @Appeon 05 February, 2021
#3
Hi Tobias,

Can you tell us:
1. Does it work well if you use the previous PB version? What PB version did you use before?
2. Can you reproduce this issue if you use OLE controls to create a small case?

It would be better if you could provide a small replicable case (including PBL and the OLE Control related DLL/OCX) for us to further analyze it. We can debug and locate the cause of the issue only when our developers could reproduce the issue locally. So a small case is very important for us.

We can only see the phenomenon when remote access to your machine and can’t locate the code that has the error. So please try your best to provide a small case for us. Hope you can understand.

Regards,
Ken
Chris Pollach @Appeon 04 February, 2021
#2
Hi Tobias;

 Thank you for all the information that you provided around this crash issue!

 I will now transfer this ticket over to the main Support / Engineering team for their review & feedback. I suspect that they will take you up on the remote session invitation to have a look at what is going on. They may also use other debugging tools & procedures that might be helpful in this investigation.

Regards ... Chris
Tobias Roth 04 February, 2021
#1
attachments.zip (33KB)

Hi,

we have one big issue after migrating to PB2019R3.

Migrate and Fullbuild is done. The error occurs in PB2019R3 before migrating and also after migrate/fullbuild .

The application crashes after loading OleCustomControl a few times.

The following OLE controls are used:
- rmpHTML.HTMLed (nBit HTML Editor )
- GdPicturePro5.GdViewer

If you want i can give you remote control to our migration machine.

I have found a Bugfix Entry in the Changelog, maybe this could have something to do with the bug:
(Bug ID: 5551) When executing CloseUserObject to close a user object that contains an OLE, IDE as well as the PB application both will crash.

Thanks

Last Lines of PBDebug tracing:
see Picture in attachment.zip

Application error:
Name der fehlerhaften Anwendung: PB190.exe, Version: 19.2.0.2670, Zeitstempel: 0x6009628d
Name des fehlerhaften Moduls: MSVBVM60.DLL, Version: 6.0.98.48, Zeitstempel: 0x5ea8e7bc
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00002fcb
ID des fehlerhaften Prozesses: 0x%9
Startzeit der fehlerhaften Anwendung: 0x%10
Pfad der fehlerhaften Anwendung: %11
Pfad des fehlerhaften Moduls: %12
Berichtskennung: %13
Vollständiger Name des fehlerhaften Pakets: %14
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: %15

.NET Runtime:
Anwendung: PB190.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 666D2FCB
Stapel:

Windows Error Reporting: (wer-file attached)
Fehlerbucket 2296687540927880487, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: PB190.exe
P2: 19.2.0.2670
P3: 6009628d
P4: MSVBVM60.DLL
P5: 6.0.98.48
P6: 5ea8e7bc
P7: c0000005
P8: 00002fcb
P9:
P10:

Thanks

Regards,
Tobi
OS:
Windows 10
Platform:
64-bit
Database Type:
SAP SQL Anywhere
Database Version:
17.0.4.2100