Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add separate browser SubProcess .exe for efficient use of CEF3 #138

Closed
perlun opened this issue Jul 25, 2013 · 1 comment
Closed

Add separate browser SubProcess .exe for efficient use of CEF3 #138

perlun opened this issue Jul 25, 2013 · 1 comment

Comments

@perlun
Copy link
Member

perlun commented Jul 25, 2013

This is really not a major one, but it will definitely be good in some of the use cases:

CEF3 uses a multi-process execution model as explained here. This means that in essence, CEF will start up a new process of your main .exe, which takes care of rendering, executing Javascript etc etc. This might be a problem if the main .exe process is big (say 100 MiB).

However, question 18 in the CEF FAQ suggest a pretty nice workaround. I think we should consider making a C++ binary based on this and ship it with CefSharp.

perlun added a commit that referenced this issue Aug 3, 2013
…ct the case when we are the rendering process, so we shutdown once CEF is done. :) Obviously, we should fix #138 and I started looking into it but it seemed non-trivial so it will have to wait a little bit further until we do it.
@perlun
Copy link
Member Author

perlun commented Aug 5, 2013

Actually, this one isn't so unimportant and should be fixed.

perlun added a commit that referenced this issue Aug 5, 2013
… changes in CEF. I have some ideas about how to approach this, but I believe we should fix #138 first.
perlun added a commit that referenced this issue Aug 22, 2013
…rt the "minimal subprocess" approach suggested by the CEF FAQ.
perlun added a commit that referenced this issue Aug 22, 2013
…tional. This will be utilized to attempt to provide e.g. a synchronous Javascript experience, albeit CEF3:s asynchronous nature.
@perlun perlun closed this as completed Aug 22, 2013
perlun added a commit that referenced this issue Oct 25, 2013
…oes it for us. I think the project was previously uncompilable with VS2010.
perlun added a commit that referenced this issue Oct 25, 2013
…e had to resort to some really, really ugly code. :( I think we should drop VS2010 support some day. It forces us to write more ugly code than otherwise.
perlun added a commit that referenced this issue Oct 25, 2013
…set up correctly. The SubProcess now compiles on Release/x64 also.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant