[Bug 37797] Warframe updater/installer crashes (CEF3 with Blink/Google Chrome and V8 checks requested font facename, doesn't like Liberation replacement, Arial font)

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Dec 28 13:31:47 CST 2014


https://bugs.winehq.org/show_bug.cgi?id=37797

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download, Installer
             Status|UNCONFIRMED                 |RESOLVED
                URL|                            |http://content.warframe.com
                   |                            |/dl/Warframe.msi
                 CC|                            |focht at gmx.net
         Resolution|---                         |DUPLICATE
            Summary|Warframe updater fails      |Warframe updater/installer
                   |                            |crashes (CEF3 with
                   |                            |Blink/Google Chrome and V8
                   |                            |checks requested font
                   |                            |facename, doesn't like
                   |                            |Liberation replacement,
                   |                            |Arial font)

--- Comment #2 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

confirming.

The crash is within CEF3 renderer processes, 'libcef.dll'

https://code.google.com/p/chromiumembedded/wiki/GeneralUsage

--- quote ---
CEF3 runs using multiple processes. The main process which handles window
creation, painting and network access is called the “browser” process. This is
generally the same process as the host application and the majority of the
application logic will run in the browser process. Blink rendering and
JavaScript execution occur in a separate “render” process. 
--- quote ---

--- snip ---
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x10ea546a).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:10ea546a ESP:0033e5c8 EBP:0033e5d4 EFLAGS:00210246(  R- --  I  Z- -P- )
 EAX:00000000 EBX:35480000 ECX:00000000 EDX:00000001
 ESI:0033e670 EDI:37b141e0
...
Backtrace:
=>0 0x10ea546a in libcef (+0xea546a) (0x0033e5d4)
  1 0x10ea8a68 in libcef (+0xea8a67) (0x0033e600)
  2 0x10e68a0d in libcef (+0xe68a0c) (0x0033e81c)
  3 0x10e68d10 in libcef (+0xe68d0f) (0x0033e85c)
  4 0x10e6c516 in libcef (+0xe6c515) (0x0033e8a8)
  5 0x10eb1c5a in libcef (+0xeb1c59) (0x0033e9a4)
  6 0x10e996d2 in libcef (+0xe996d1) (0x0033e9c8)
...

Wine-dbg>info process
 pid      threads  executable (all id:s are in hex)
 00000060 28       'Launcher.exe'
 0000005d 12       \_ 'Launcher.exe'
 00000076 2           \_ 'winedbg.exe'
 00000022 1        'explorer.exe'
 0000000e 5        'services.exe'
 00000019 3        \_ 'plugplay.exe'
 00000012 4        \_ 'winedevice.exe'
 00000008 1        'Launcher.exe'
 0000002c 11       \_ 'Launcher.exe'
--- snip ---

Dumping the version info from 'libcef.dll' with 'resourcehacker' yields:

--- snip ---
1 VERSIONINFO
FILEVERSION 3,2062,1838,0
PRODUCTVERSION 3,2062,1838,0
FILEOS 0x4
FILETYPE 0x2
{
BLOCK "StringFileInfo"
{
    BLOCK "040904b0"
    {
        VALUE "FileDescription", "Chromium Embedded Framework (CEF) Dynamic
Link Library"
        VALUE "FileVersion", "3.2062.1838"
        VALUE "InternalName", "libcef"
        VALUE "LegalCopyright", "Copyright (C) 2014 The Chromium Embedded
Framework Authors"
        VALUE "OriginalFilename", "libcef.dll"
        VALUE "ProductName", "Chromium Embedded Framework (CEF) Dynamic Link
Library"
        VALUE "ProductVersion", "3.2062.1838"
    }
}
--- snip ---

http://cefbuilds.com/#branch_2062

Fortunately it seems they use an unmodified CEF3 build 3.2062.1838 after
comparing the provided downloads and the API hash which helped me a bit during
debugging and to nail it further down.

It seems the problem stems from font subsystem being not happy about the
returned font facenames requested.
Not a surprise - similar situation as with Webkit based apps.

'winetricks -q corefonts' (or Arial font alone) prevents the crash.

Also Patrick's patch https://bugs.winehq.org/attachment.cgi?id=50082 from
https://bugs.winehq.org/show_bug.cgi?id=32342#c19 helps here.

Resolving as dupe.

Regards

*** This bug has been marked as a duplicate of bug 32342 ***

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.


More information about the wine-bugs mailing list