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

Resolved PB2019 R3 crashing on libcef.dll

  1. Issue
0
Votes
Undo
  1. Mickey Hillel
    Mickey Hillel
  2. PowerBuilder
  3. Thursday, 24 June 2021 08:03 AM UTC

Hi,

We are experiencing many crashes with PB2019 R3 Build 2703.

All are related to libcef.dll

This is happening in both development environment , Windows Server 2019, and also on our production environment,  Windows Server 2012.

The crashes seem to be random, I can't find any specific action or event that is causing.

Following is the event viewer log from our development platform: 

Faulting application name: PB190.exe, version: 19.2.0.2703, time stamp: 0x6065b6d0
Faulting module name: libcef.dll, version: 3.3626.1894.0, time stamp: 0x5c591850
Exception code: 0xc0000005
Fault offset: 0x0028bb3a
Faulting process id: 0x8364
Faulting application start time: 0x01d7683112755e67
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.exe
Faulting module path: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2703\pbcef\libcef.dll
Report Id: 05878b6d-b058-46ea-9166-13a340813b3d

From our production server : 

Faulting application name: XXXXXX.exe, version: 139.2.0.0, time stamp: 0x6065b68d
Faulting module name: libcef.dll, version: 3.3626.1894.0, time stamp: 0x5c591850
Exception code: 0xc000041d
Fault offset: 0x0028bb3a
Faulting process id: 0x8524
Faulting application start time: 0x01d768c405ec170e
Faulting application path: C:\Program Files\CareProg\MediCare\3\medical.exe
Faulting module path: C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbcef\libcef.dll
Report Id: 828bcad6-d4b8-11eb-8352-00155d0a092b

 

Any help would be appreciated in resolving this.

TIA

Mickey Hillel

 

 

 

 

 

  1. Crash
  2. PowerBuilder (Appeon)
Response window position on dual monitor setup
How to access html file using MicrodoftEdge
Accepted Answer
Mickey Hillel
Mickey Hillel Accepted Answer Pending Moderation
  1. Thursday, 24 June 2021 09:04 AM UTC
  2. PowerBuilder
  3. # Permalink

Thank you for that information.

In fact we added a webbrowser control to one of our windows, so atleast I can disable it till we find what the problem is.

Anyone else encountered this crash? 

Comment
Pieter Coene
  1. Pieter Coene
  2. Wednesday, 30 June 2021 15:20 PM UTC
Hi Mickey,



we also use this new webbrowser control to show a page with the 'Openlayers' library. Our customers uses this windows (with the webbrowser control) al lot and are complaining that it sporadicly crashes (sometimes a few times a day). We can't simulate it in-house so i have no idea what is causing this crash.



In the event-viewer of the customer, i saw the same output from the crash (libcef.dll).



i noticed that the version noted (3.3626.1894.0) looks like a build from 2019. I don't know if there are any plans to upgrade this version?



Greetz

Pieter
  1. Helpful
There are no comments made yet.
Responses (6)
Tomas Beran
Tomas Beran Accepted Answer Pending Moderation
  1. Thursday, 5 May 2022 17:35 PM UTC
  2. PowerBuilder
  3. # 1

Hi

I'm getting this error (libcef, offset 0x0028bb3a) when I call close(window) from  a webbrowser event. The workaround is to call close(window) through PostEvent.

PB2021 build 1509

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 5 May 2022 17:57 PM UTC
Hi Tomas ... FYI: there is a related (I think) ticket in the Support System that highlights this (and other side effects) if a Navigate() process is still underway. Engineering is looking at this currently in light of the newer Chromium engine upgrade for PB2022.
  1. Helpful 1
Tomas Beran
  1. Tomas Beran
  2. Friday, 6 May 2022 09:49 AM UTC
Hi Chris

Navigate() was an issue on MS web browser OCX too. So I'm prepared for it and I do it as much thread safe as possible. What I investigated yesterday was the following:

1. Open webbrowse

2. Download a picture through navgigate()

3. Wait until 100%, NavigationStateChanged and TitleTextChanged (all these condittions must be met, simulates "navigated" event)

4. Register ue_clicked event to webbrowse object

5. Inject javascript event ue_clicked to the picture using EvaluateJavascriptSync (simulates non existing "Clicked")

6. add code "close(parent)" to ue_clicked event of the webbrowse object



Now if you do this then two things happen:

1. Number of threads grows with every opening of the window

2. After 10-20 opening the app crashes in libcef.dll at 0x0028bb3a offset.

I'm not sure with this but it looked like even I close the app correctly then next instance of the app crashed faster.

Using PostEvent in ue_clicked event solved the issue.

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 6 May 2022 12:47 PM UTC
Hi Tomas ... Thank you for that detailed information & observations. The new PB2022 will have a much newer Chromium web engine "under the PB hood". If you have a good test case for this issue (there are current support tickets open for these issues), then you can test the updated web control in PB2022 beta arriving in June.

Regards ... Chris
  1. Helpful
There are no comments made yet.
René Ullrich
René Ullrich Accepted Answer Pending Moderation
  1. Thursday, 24 June 2021 08:50 AM UTC
  2. PowerBuilder
  3. # 2

Hi Mickey,

I think libcef.dll is part of the WebBrowser control.

Maybe this helps you to find out what could be the reason.

René

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 24 June 2021 14:07 PM UTC
  2. PowerBuilder
  3. # 3

Hi Mickey;

   FYI: Please note that the PB IDE is not certified for use with any MS-Windows "server" editions. In your case W2019.

http://docs.appeon.com/pb2019r3/release_bulletin_for_pb/system_requirements.html

  App EXE's built from the IDE though are Windows "Server" capable.

Regards ... Chris

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 30 June 2021 16:06 PM UTC
  2. PowerBuilder
  3. # 4

Hi Mickey,

I had the use of CEF crashing my application when closing the app (only on windows server 2012 R2) and there's a workaround.

https://www.appeon.com/standardsupport/track/view?id=6851

regards.

Comment
There are no comments made yet.
Tomas Beran
Tomas Beran Accepted Answer Pending Moderation
  1. Tuesday, 26 April 2022 16:15 PM UTC
  2. PowerBuilder
  3. # 5

Hi

Just FYI. I've got this bug at PB2021. Application running from IDE. W10. The app+ide had been randomly crashing few seconds after closing of window which contains webbrowser object until I've applied the workaround mentioned above.

Same offset, same process name as the OP.

Faulting application name: PB210.exe, version: 21.0.0.1506, time stamp: 0x61e55eac
Faulting module name: libcef.dll, version: 3.3626.1894.0, time stamp: 0x5c591850
Exception code: 0xc0000005
Fault offset: 0x0028bb3a
Faulting process id: 0x2b04
Faulting application start time: 0x01d859702bcb3325
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 21.0\PB210.exe
Faulting module path: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 21.0.0.1506\pbcef\libcef.dll
Report Id: 5bffd2e0-6fc2-48bc-87fe-1222422fa24f
Faulting package full name:
Faulting package-relative application ID:

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.