Page 1 of 2

Update to CEF 77.1.3 (BETA)

Posted: Tue Oct 01, 2019 5:07 pm
by salvadordf
Hi,

I created a BETA branch for the update to CEF 77.1.3.

It's not possible to disable the "Network Service" in the new CEF version and this new branch has an issue when you close the application.

Sometimes, the application has an access violation when the application is closed and I'm still debugging the demos to find out why is this happening.

It looks like the demos that allow you to close all the browsers and wait a little until the application is closed don't crash but it's too soon to be certain.

This is what's new :
  • Chromium 77.0.3865.90
  • Added GlobalCEFApp.EnablePrintPreview. It shows a print preview like Chrome/Chromium when you print a web page.
  • Removed the "Audio Handler". CEF removed it because it has to be reimplemented to support out of process audio.
The CEF binaries are these :

Re: Update to CEF 77.1.3 (BETA)

Posted: Wed Oct 02, 2019 4:40 pm
by salvadordf
I added the debug trace about this issue in the CEF project :
https://bitbucket.org/chromiumembedded/ ... closing-if

Re: Update to CEF 77.1.3 (BETA)

Posted: Sun Oct 06, 2019 2:59 pm
by salvadordf
I did many tests and it seems that closing all the browsers and waiting for a second before closing the main form is a "safe" workaround. (notice the quotes).

In addition to that, you can also get the amount of child processes with GlobalCEFApp.ChildProcessesCount and close the main form only when there're 2 child processes corresponding to the gpu and utility processes created when CEF is initialized.

I managed to reproduce this problem with the official CEF sample application and added the trace and dump in the CEF project issue.

Re: Update to CEF 77.1.3 (BETA)

Posted: Mon Oct 07, 2019 4:37 pm
by thefunkyjoint
I'm trying to test this beta, but get this error on opening... I downloaded the binaries from the link provided in this topic.

Re: Update to CEF 77.1.3 (BETA)

Posted: Mon Oct 07, 2019 4:47 pm
by salvadordf
I uploaded several new versions to the BETA branch since then. Use the links in the "readme.md" file :
32 bits -> http://opensource.spotify.com/cefbuilds ... 32.tar.bz2
64 bits -> http://opensource.spotify.com/cefbuilds ... 64.tar.bz2

The CEF project maintainer fixed a crash today. That means that the beta branch will probably be updated tomorrow.

Re: Update to CEF 77.1.3 (BETA)

Posted: Mon Oct 07, 2019 4:49 pm
by thefunkyjoint
Great, it's working now, thanks !

Re: Update to CEF 77.1.3 (BETA)

Posted: Mon Oct 07, 2019 5:35 pm
by thefunkyjoint
So i'm having this weird bug / crash in some pages, where one of the following things happens :

1 - App crash and closes

2 - The page goes blank and unresponsive after navigating.

When both problems happens and i close my app, i can check on the task manager the related subprocesses keeps running and i have to force close them.

This happens randomly, usually in pages with big content size (Facebook groups for instance).

I've noticed when i use GlobalCEFApp.SingleProcess := true; this issue tends to happen less often...

Tried this beta hope this issue would be fixed, but still happens, at least when not using SingleProcess := true...

Any hints about this ? :roll:

Re: Update to CEF 77.1.3 (BETA)

Posted: Mon Oct 07, 2019 6:07 pm
by Paulo França
I was facing so many crashes on app termination that I've decided to stick with CEF v75 and the SingleProcess model. As a result, ALL crashes are gone!

Re: Update to CEF 77.1.3 (BETA)

Posted: Mon Oct 07, 2019 6:35 pm
by thefunkyjoint
Paulo França wrote: Mon Oct 07, 2019 6:07 pm I was facing so many crashes on app termination that I've decided to stick with CEF v75 and the SingleProcess model. As a result, ALL crashes are gone!
Everything was fine for me until this version too. It seems CEF builds after that changed something that are causing the crashes...

Re: Update to CEF 77.1.3 (BETA)

Posted: Mon Oct 07, 2019 7:10 pm
by salvadordf
thefunkyjoint wrote: Mon Oct 07, 2019 5:35 pm So i'm having this weird bug / crash in some pages, where one of the following things happens :
1 - App crash and closes
2 - The page goes blank and unresponsive after navigating.
The "blank and unresponsive page" error is usually a render process crash. It would be necessary to debug that process to get more clues.