Is CEF (Chromium Embedded Framework) supported by Chromium developers?

[edwabr123]

I am asking this because there is a long time issue of CEF crashing on Mac OS X making it not usable. In short Chromium cannot be embedded into a widget/application because calling CefDoMessageLoopWork will result in a crash when application exits. Here is the link that describes the issue http://www.magpcss.org/ceforum/viewtopic.php?f=6&t=11922

[Torne (Richard Coles)]

On 13 August 2014 16:30, edwabr123 <edwa...@gmail.com> wrote:

I am asking this because there is a long time issue of CEF crashing on Mac OS X making it not usable. In short Chromium cannot be embedded into a widget/application because calling CefDoMessageLoopWork will result in a crash when application exits. Here is the link that describes the issue http://www.magpcss.org/ceforum/viewtopic.php?f=6&t=11922

No, it's a third party project.

 

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

[edwabr123]

I understand it's a third party project and no direct support is provided, but i am wondering if Chromium developers are paying attention to the issues CEF is having, the issues that can only be resolved by modifying Chromium code. If there is no such support from Chromium then in my opinion it's pretty much risky to build a CEF based application.

[Torne (Richard Coles)]

On 13 August 2014 16:53, edwabr123 <edwa...@gmail.com> wrote:

I understand it's a third party project and no direct support is provided, but i am wondering if Chromium developers are paying attention to the issues CEF is having, the issues that can only be resolved by modifying Chromium code. If there is no such support from Chromium then in my opinion it's pretty much risky to build a CEF based application.

No, nobody is paying attention to CEF probably. If people from CEF file bugs on the chromium bug tracker about issues they find that are actually in chromium code, we will see them and probably fix them, but other than that probably nothing.

[edwabr123]

But those bugs being reported are not of high priority, are they? I guess CEF is not the use case Chromium target at?

[Torne (Richard Coles)]

On 13 August 2014 17:11, edwabr123 <edwa...@gmail.com> wrote:

But those bugs being reported are not of high priority, are they? I guess CEF is not the use case Chromium target at?

If the issue affects Chromium (and just happened to be discovered by someone working with CEF) then it's as high priority as anything else. If it doesn't actually affect Chromium and is only an issue because of something CEF is doing then it depends what it would take to fix and whether it would have any negative impact on anything we support, and if the people who know the code in question feel like doing it.

 

On Wednesday, August 13, 2014 8:01:06 PM UTC+4, Torne (Richard Coles) wrote:

No, nobody is paying attention to CEF probably. If people from CEF file bugs on the chromium bug tracker about issues they find that are actually in chromium code, we will see them and probably fix them, but other than that probably nothing.

 

--

[edwabr123]

The problem with CEF is that it has to be based on current version of Chromium, to be up to date with the new Chromium features. It cannot be based on a Chromium fork, so guys from CEF can fix issues themselves, instead they have to wait till guys from Chromium pay attention to the issues they are having. I doubt such shaky collaboration can result in a good product (CEF) that can be used in a serious project.

[Philip Rogers]

Why can't CEF folks fix Chromium issues?

--

--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[edwabr123]

The whole idea is CEF being up to date with the features Chromium currently has. I mean HTML5, performance and other stuff. Once they fork Chromium they are stuck with Chromium code they cannot update.

[Philip Rogers]

Correct, they can't practically work on a fork.

You said "they have to wait till guys from Chromium pay attention to the issues they are having" and I'm wondering why they have to wait for Chromium to fix the issues instead of fixing it themselves in Chromium?

[edwabr123]

Are they allowed to do so? Is anyone from CEF development group also participates in Chromium development? Is he allowed to make changes to the code he didn't write?

[Philip Rogers]

Of course they are allowed to. Chromium is real open source :)

[edwabr123]

But there must a procedure to accept the modifications, so they do not ruin the other use cases. So, it's not like someone from outside comes and makes changes to the code and next version of Chromium comes with them. There sure is a procedure of accepting the changes and i guess that procedure is pretty cautious about introducing changes that solve issues no one actually cares about (related to CEF). I might myself try to go this route, become a Chromium contributor and try to fix the CEF issue i mentioned in the beginning. I have 15+ experience in system programming and probably will be able to find the root cause. But again i doubt management will allow me to make changes that fix unimportant issues but may affect the target solutions.

[Czarek Tomczak]

On Wednesday, August 13, 2014 7:17:45 PM UTC+2, edwabr123 wrote:

But there must a procedure to accept the modifications, so they do not ruin the other use cases. ......

CEF applies many patches to Chromium during build, see:
https://code.google.com/p/chromiumembedded/source/browse/trunk/cef3/patch/patches/

[Czarek Tomczak]

And the patch README:
https://code.google.com/p/chromiumembedded/source/browse/trunk/cef3/patch/README.txt