CEF Mac OS X test app doesn't display anything

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download CEF Test App from http://cefbuilds.com/
2. Run it
3. Enter an URL and press enter

I expected to see the web site, instead, I see a blank page. This is running on 
Mac OS X Yosemite, up to date. I tried both 2272 as well as dev trunk. By 
watching the URL and title, I can see redirects are being followed and 
something is being loaded.

We are considering using CEF on a Mac OS X application (we are already using it 
on the Windows version) but without the reference integration working is hard 
to know why ours is failing.

Original issue reported on code.google.com by pup...@pupeno.com on 25 Feb 2015 at 10:58

Attachments:

• [Screen Shot 2015-02-25 at 10.57.50.png](https://storage.googleapis.com/google-code-attachments/chromiumembedded/issue-1547/comment-0/Screen Shot 2015-02-25 at 10.57.50.png)

[GoogleCodeExporter]

What Mac hardware? Is there any output if you run the sample app from the 
console?

$ ./path/to/cefclient.app/Contents/MacOS/cefclient

Original comment by magreenb...@gmail.com on 25 Feb 2015 at 3:58

[GoogleCodeExporter]

Also, you can try building cefclient/cefsimple locally using the binary 
distribution to see if that makes a difference.

Original comment by magreenb...@gmail.com on 25 Feb 2015 at 4:14

[GoogleCodeExporter]

I just experienced the same behavior on the following system:

OS X Version 10.9.4
Macbook Pro 2.4 GHz Core i7
16 GB RAM

I tried the two suggestions above but neither changed the behavior. The 
mouseover appears to be working as well as the title bar but nothing is 
rendered.

After trying these I downloaded a couple of the older branches and tried the 
precompiled cefclient.app from them.

These are the results:
3.2272.2050  OS X x64 - No display
3.1650.1639 OS X x32 - Displays
3.2171.2069 OS X x64 - Displays

It would appear that something more recent than branch 2171 is the problem.

Original comment by Nny....@gmail.com on 12 Mar 2015 at 6:09

[GoogleCodeExporter]

@#3: Please try running from the console as described in #1 to see if there's 
any output.

Original comment by magreenb...@gmail.com on 12 Mar 2015 at 4:00

[GoogleCodeExporter]

@#4: After attempting the suggestions in #1 and #2 for trunk and branch 2272 it 
did not change the behavior.

Original comment by Nny....@gmail.com on 12 Mar 2015 at 6:16

[GoogleCodeExporter]

This is hitting me, too.  Here's my results on OSX 10.9 64 bits, 
on a Macbook Pro, doing a local build of cefclient (i.e. not using the 
downloaded test app):

cef_binary_3.2171.1902_macosx64: ok
cef_binary_3.2171.1979_macosx64: ok
cef_binary_3.2272.2029_macosx64: ../cefclient/test_runner.cc:19:10: fatal 
error: cefclient/resource.h file not found
cef_binary_3.2272.2068_macosx64: Page title loads, but body empty
cef_binary_3.2321.2067_macosx64: Page title loads, but body empty

Running it from the console shows no output on stdout/err, even when building 
for debug with -DCMAKE_BUILD_TYPE=Debug.

I guess I could bisect a little... is there any data I could gather to help 
narrow this down?

Original comment by daniel.r...@gmail.com on 12 Mar 2015 at 8:42

[GoogleCodeExporter]

More data:

cef_binary_2272.1998_macosx64: Page title loads, but body empty (had to copy in 
resource.h by hand from 2272.2068 to get it to build)

So branch 2272 is bad pretty much back to the beginning.
Maybe the breakage is related to the new version of chromium (41.0.2272.16) 
that branch 2272 brought in.

Original comment by daniel.r...@gmail.com on 12 Mar 2015 at 9:52

[GoogleCodeExporter]

CEF is transitioning from Google Code to Bitbucket project hosting. If you 
would like to continue receiving notifications on this issue please add 
yourself as a Watcher at the new location: 
https://bitbucket.org/chromiumembedded/cef/issue/1547

Original comment by magreenb...@gmail.com on 14 Mar 2015 at 3:38

[GoogleCodeExporter]

The bitbucket link above currently returns "Internal Server Error"

Original comment by daniel.r...@gmail.com on 16 Mar 2015 at 3:51

[GoogleCodeExporter]

It's back up, link works again.  I should have waited a minute.

Original comment by daniel.r...@gmail.com on 16 Mar 2015 at 3:53