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

cefclient renders blank OOPIF with --off-screen-rendering-enabled #2578

Closed
magreenblatt opened this issue Jan 22, 2019 · 7 comments
Closed
Labels
bug Bug report

Comments

@magreenblatt
Copy link
Collaborator

Original report by Kailai Wang (Bitbucket: Kailai, GitHub: Kailai).


What steps will reproduce the problem?

  1. run cefclient with
    ./cefclient --site-per-process --url="http://csreis.github.io/tests/cross-site-iframe.html" --off-screen-rendering-enabled

  2. click on "Go cross-site (complex page)" button

  3. only white iframe is rendered

What is the expected output? What do you see instead?

Expected: the contents of http://build.chromium.org should be seen

Observed: just blank page (see attached screenshot).
"Go cross-site (simple page)" and "Go same-site" works fine.

I could see that there's extra renderer process for this iframe and from logs at least it tries to load the resources, it's just somehow the final rendering is missing.

I'm not sure if the problem is related to Issue #2577 or not though.

What version of the product are you using? On what operating system?

I'm using the latest 3578 cef branch. I tried to build it from the sources, and to use the distributed binary "cef_binary_3.3578.1864.gfa073f3_linux64.tar.bz2", unfortunately neither did work as expected.

Tested on a Ubuntu 16.04.5 LTS 64 bit machine.

Does the problem reproduce with the cefclient or cefsimple sample application at the same version? How about with a newer or older version?

Untested

Does the problem reproduce with Google Chrome at the same version? How about with a newer or older version?

Chrome works fine, as it probably doesn't have osr flag.

@magreenblatt
Copy link
Collaborator Author

How does it behave without the --site-per-process flag?

@magreenblatt
Copy link
Collaborator Author

Original comment by Kailai Wang (Bitbucket: Kailai, GitHub: Kailai).


Without --site-per-process it works as expected, there's then only 1 renderer process though.

With --site-per-process there're 3.

@magreenblatt
Copy link
Collaborator Author

Original changes by Kailai Wang (Bitbucket: Kailai, GitHub: Kailai).


  • edited description

1 similar comment
@magreenblatt
Copy link
Collaborator Author

Original changes by Kailai Wang (Bitbucket: Kailai, GitHub: Kailai).


  • edited description

@magreenblatt
Copy link
Collaborator Author

Original comment by Salvador Diaz Fau (Bitbucket: salvadordf, GitHub: salvadordf).


This could be related to #2498/add-support-for-site-per-process

@magreenblatt
Copy link
Collaborator Author

Duplicate of #2498.

@magreenblatt
Copy link
Collaborator Author

  • changed state from "new" to "duplicate"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report
Projects
None yet
Development

No branches or pull requests

1 participant