branch 1750 binaries don't work on XP - not a valid Win32...

[Czarek]

I've been testing the following TestApp binaries from cefbuilds.com on Windows XP SP3:

Code: Select all

cef_binary_3.1650.1639_windows32_client
cef_binary_3.1750.1805_windows32_client
cef_binary_3.1916.1804_windows32_client
cef_binary_3.2062.1803_windows32_client
cef_binary_3.2078.1802_windows32_client


All work fine except "cef_binary_3.1750.1805_windows32_client". When running this binary on XP SP3 I get an error:

Code: Select all

C:\...\cefclient.exe is not a valid Win32 application.


On Win7 that same binary works fine, so it's not a download error or anything like that.

[Czarek]

Tested "cef_binary_3.1750.1805_windows32_client" on an another XP SP3 machine (a clean install of XP) and the same error appears "is not a valid Win32 application".

[magreenblatt]

Tested "cef_binary_3.1750.1805_windows32_client" on an another XP SP3 machine (a clean install of XP) and the same error appears "is not a valid Win32 application".

It's a bit strange that it would only be a problem with 1750 branch. Can you open cefclient.exe and libcef.dll in Dependency Walker and see if it complains about any missing symbols or libraries?

[Czarek]

I don't see anything unusual in Dependency Walker. Attaching screenshot + DWI image exported.

It must be noted that both of these machines have only XP SP3 update, they do not include any subsequent updates after SP3 (and I resemble there is about a hundred or more of them to download through automatic updates).

I have also tried running an XP SP3 VM image with many updates applied after SP3, but the error is still the same. However I see dozens of new updates that appeared after November 2013, I will install them and see if that changes anything.

[Czarek]

When opening "cef_binary_3.2078.1802_windows32_client" in Dependency Walker, the results are identical.

I have installed all Windows Updates on the XP SP3 VM image mentioned earlier, and the error still persists. Tested 1916 branch on that machine as well and it works perfectly fine.

[Czarek]

I have compared resources embedded in 1750 and 1916 binaries using Resource Hacker and there are some differences. In branch 1750 cefclient.exe is missing the xml header in its assembly manifest (resource 24/1/1033):

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


Also, in branch 1750 the libcef.dll and ffmpegsumo.dll libraries are missing assembly manifest (resource 24/2/1033). This manifest is embedded in branch 1916 dlls. However I've tried removing these manifests from branch 1916 binaries and cefclient still launched fine, so this is not the cause of "not a valid win32 application" error.

[Czarek]

Found the cause of the issue. PE32 headers for cefclient.exe (1750) show system version 6.0 (Vista). In other branches PE32 headers show system version 5.1 (Windows XP). It was checked using Exe Explorer.

[Czarek]

Obviously in branch 1750 on cefbuilds.com the target platform is set to Vista or later, for the build of TestApp. I've downloaded "cef_binary_3.1750.1805_windows32", opened cefclient2010.sln and built cefclient. The result binaries run fine on XP. So the issue must be in the configuration of automated build tools for TestApp on cefbuilds.com (branch 1750 only).