cef3, single-process mode, cleaning up at the wrong time?

[edwinyzh]

Hi Marshall,

I'm using cef3 in single-process mode (for some good reasons), I found that if my program end all existing browser instances, then all newly created browser instances will stop working - no websites or strings can be loaded anymore.

So I suspect when a cef3 instance is being destroyed, it checks if there is still any other live browser instance, if no, it wrongly does some cleanup that's not supposed to be doing unless the entire program is shutting down?

I'm using the Delphi wrapper of cef3 and the developer confirms the Delphi wrapper doesn't do any cleanup and he guess the problem is coming from cef3, so I'm asking for help here. The original discussion.

cef3 is really great and this is the only main problem I'm experiencing.

[magreenblatt]

Single process mode is intended as a development/debugging tool and is not recommended for production use. There are many potential bugs and stability issues related to use of single process mode. You should strongly consider making your application work in multi process mode.

[edwinyzh]

Single process mode is intended as a development/debugging tool and is not recommended for production use. There are many potential bugs and stability issues related to use of single process mode. You should strongly consider making your application work in multi process mode.

Sad to hear that... Actually I want to use cef3 in single-process mode, because my app exposes a wide variety of objects to the JavaScript environment, and in single-process mode things are much easier, because in multi-process mode "object A in process A" cannot directly access "object B in process B"...

[Czarek]

A "hacky" solution would be to create a hidden browser window that does not load anything, just exists for the whole time application being.

[Czarek]

...There are many potential bugs and stability issues related to use of single process mode...

And there is no plan to fix them in the future? The only proper way is to go multi-process mode?

[magreenblatt]

Single process mode is intended as a development/debugging tool and is not recommended for production use. There are many potential bugs and stability issues related to use of single process mode. You should strongly consider making your application work in multi process mode.

Sad to hear that... Actually I want to use cef3 in single-process mode, because my app exposes a wide variety of objects to the JavaScript environment, and in single-process mode things are much easier, because in multi-process mode "object A in process A" cannot directly access "object B in process B"...

In this case you might consider using CEF1 which is a stable single-process implementation.

[magreenblatt]

...There are many potential bugs and stability issues related to use of single process mode...

And there is no plan to fix them in the future? The only proper way is to go multi-process mode?

Most of the stability issues are in Chromium code, and the single-process code path gets very little real world usage and testing currently. Any issues will likely be fixed in the future (Chromium for mobile devices needs a stable single-process mode) but the timeline is undefined.

[edwinyzh]

Single process mode is intended as a development/debugging tool and is not recommended for production use. There are many potential bugs and stability issues related to use of single process mode. You should strongly consider making your application work in multi process mode.

Sad to hear that... Actually I want to use cef3 in single-process mode, because my app exposes a wide variety of objects to the JavaScript environment, and in single-process mode things are much easier, because in multi-process mode "object A in process A" cannot directly access "object B in process B"...

In this case you might consider using CEF1 which is a stable single-process implementation.

Yes, I was using cef1 and it's very stable, but I thought cef3 is the new cef and cef1 is (or will be) out of date. So here are you suggesting that cef1 will be kept updating like cef3 in the future?

[fddima]

Most of the stability issues are in Chromium code, and the single-process code path gets very little real world usage and testing currently. Any issues will likely be fixed in the future (Chromium for mobile devices needs a stable single-process mode) but the timeline is undefined.

In other side - chrome for android already published - it is really still buggy even on android, but have chances to fixed more quickly, than last year.

[magreenblatt]

Yes, I was using cef1 and it's very stable, but I thought cef3 is the new cef and cef1 is (or will be) out of date. So here are you suggesting that cef1 will be kept updating like cef3 in the future?

There are no plans currently to end support for CEF1. If you want stable single-process mode at this time it is better to use CEF1 instead of CEF3. You may eventually want to port your application to CEF3 multi-process mode in order to take advantage of the stability, security, performance and feature improvements.