Disclosure Statement: This site contains affiliate links, which means that I may receive a commission if you make a purchase using these links. As an eBay Partner, I earn from qualifying purchases.
If you find these projects useful please consider becoming a sponsor with Patreon, GitHub or Liberapay.

Appcrash ChromeRuntime

win568neu
Posts: 29
Joined: Thu May 23, 2024 6:36 am

Re: Appcrash ChromeRuntime

Post by win568neu »

Hi Salvador

I am using the Deug version 130.1.3 provided on cef-builds.spotifycdn.com with the corresponding debug symbols. When I try to reload I get the following error

Code: Select all

0:069> .reload /f libcef.dll
SYMSRV:  BYINDEX: 0x3
         c:\symbols*http://msdl.microsoft.com/download/symbols
         libcef.dll.pdb
         F2462CFBF204D2CC4C4C44205044422E1
SYMSRV:  PATH: c:\symbols\libcef.dll.pdb\F2462CFBF204D2CC4C4C44205044422E1\libcef.dll.pdb
SYMSRV:  RESULT: 0x00000000
DBGHELP: c:\symbols\libcef.dll.pdb\F2462CFBF204D2CC4C4C44205044422E1\libcef.dll.pdb - file system or network error reading pdb
DBGHELP: c:\cef\libcef.dll.pdb - file system or network error reading pdb
DBGHELP: libcef.dll.pdb - file not found
*** WARNING: Unable to verify checksum for c:\cef\libcef.dll
DBGHELP: libcef - export symbols
win568neu
Posts: 29
Joined: Thu May 23, 2024 6:36 am

Re: Appcrash ChromeRuntime

Post by win568neu »

Hi

After reinstalling the Windows SDK, i got this, when i come to the Point, where the App crashes.
WinDbg x64 is not able to load the Debug Symbols from Pdb (mismatch)

Code: Select all

ModLoad: 00000000`6a560000 00000000`6a579000   C:\WINDOWS\SysWOW64\MobileNetworking.dll
ModLoad: 00000000`4ce00000 00000000`4d322000   C:\Windows\SysWOW64\Windows.Media.dll
ModLoad: 00000000`4d330000 00000000`4d483000   C:\Windows\SysWOW64\InputHost.dll
(4e94.6160): WOW64 breakpoint - code 4000001f (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
864fb88e ??              ???
0:039:x86> .reload /f libcef.dll
SYMSRV:  BYINDEX: 0x6
         c:\symbols*http://msdl.microsoft.com/download/symbols
         libcef.dll.pdb
         F2462CFBF204D2CC4C4C44205044422E1
SYMSRV:  PATH: c:\symbols\libcef.dll.pdb\F2462CFBF204D2CC4C4C44205044422E1\libcef.dll.pdb
SYMSRV:  RESULT: 0x00000000
DBGHELP: c:\symbols\libcef.dll.pdb\F2462CFBF204D2CC4C4C44205044422E1\libcef.dll.pdb - mismatched pdb
DBGHELP: c:\cef\libcef.dll.pdb - mismatched pdb
DBGHELP: libcef.dll.pdb - file not found
DBGHELP: Couldn't load mismatched pdb for c:\cef\libcef.dll
*** WARNING: Unable to verify checksum for c:\cef\libcef.dll
DBGHELP: libcef - export symbols

************* Symbol Loading Error Summary **************
Module name            Error
libcef                 The system cannot find the file specified
				The SYMSRV client failed to find a file in the UNC store, or there
				is an invalid UNC store (an invalid path or the pingme.txt file is
				not present in the root directory), or the file is present in the
				symbol server exclusion list.

SYMSRV:  BYINDEX: 0x7
         c:\symbols*http://msdl.microsoft.com/download/symbols
         System.Xml.ni.pdb
         AAF9A3A05CC4690167C02C8547D222831
SYMSRV:  UNC: c:\symbols\System.Xml.ni.pdb\AAF9A3A05CC4690167C02C8547D222831\System.Xml.ni.pdb - file not found
SYMSRV:  UNC: c:\symbols\System.Xml.ni.pdb\AAF9A3A05CC4690167C02C8547D222831\System.Xml.ni.pd_ - file not found
SYMSRV:  UNC: c:\symbols\System.Xml.ni.pdb\AAF9A3A05CC4690167C02C8547D222831\file.ptr - file not found
SYMSRV:  HTTPGET: /download/symbols/index2.txt
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  HTTPGET: /download/symbols/System.Xml.ni.pdb/AAF9A3A05CC4690167C02C8547D222831/System.Xml.ni.pdb
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  HTTPGET: /download/symbols/System.Xml.ni.pdb/AAF9A3A05CC4690167C02C8547D222831/System.Xml.ni.pd_
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  HTTPGET: /download/symbols/System.Xml.ni.pdb/AAF9A3A05CC4690167C02C8547D222831/file.ptr
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  RESULT: 0x80190194
DBGHELP: C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\aaf9a3a05cc4690167c02c8547d22283\System.Xml.ni.pdb - file not found
DBGHELP: System.Xml.ni.pdb - file not found
*** WARNING: Unable to verify checksum for C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\aaf9a3a05cc4690167c02c8547d22283\System.Xml.ni.dll
DBGHELP: System_Xml_ni - no symbols loaded
DBGHELP: No debug info for C:\Program Files (x86)\BMDNTCSClients\BMDNTCS-SRV\BMDNTCS.exe.  Searching for dbg file
SYMSRV:  BYINDEX: 0x8
         c:\symbols*http://msdl.microsoft.com/download/symbols
         BMDNTCS.dbg
         67528E13350e0000
SYMSRV:  UNC: c:\symbols\BMDNTCS.dbg\67528E13350e0000\BMDNTCS.dbg - path not found
SYMSRV:  UNC: c:\symbols\BMDNTCS.dbg\67528E13350e0000\BMDNTCS.db_ - path not found
SYMSRV:  UNC: c:\symbols\BMDNTCS.dbg\67528E13350e0000\file.ptr - path not found
SYMSRV:  HTTPGET: /download/symbols/BMDNTCS.dbg/67528E13350e0000/BMDNTCS.dbg
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  HTTPGET: /download/symbols/BMDNTCS.dbg/67528E13350e0000/BMDNTCS.db_
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  HTTPGET: /download/symbols/BMDNTCS.dbg/67528E13350e0000/file.ptr
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  RESULT: 0x80190194
DBGHELP: C:\Program Files (x86)\BMDNTCSClients\BMDNTCS-SRV\BMDNTCS.dbg - file not found
DBGHELP: C:\Program Files (x86)\BMDNTCSClients\BMDNTCS-SRV\exe\BMDNTCS.dbg - path not found
DBGHELP: C:\Program Files (x86)\BMDNTCSClients\BMDNTCS-SRV\symbols\exe\BMDNTCS.dbg - path not found
DBGHELP: C:\Program Files (x86)\BMDNTCSClients\BMDNTCS-SRV\BMDNTCS.dbg - file not found
DBGHELP: C:\Program Files (x86)\BMDNTCSClients\BMDNTCS-SRV\BMDNTCS.exe missing debug info.  Searching for pdb anyway
DBGHELP: Can't use symbol server for BMDNTCS.pdb - no header information available
DBGHELP: C:\Program Files (x86)\BMDNTCSClients\BMDNTCS-SRV\BMDNTCS.pdb - file not found
DBGHELP: BMDNTCS.pdb - file not found
*** WARNING: Unable to verify checksum for C:\Program Files (x86)\BMDNTCSClients\BMDNTCS-SRV\BMDNTCS.exe
DBGHELP: BMDNTCS - export symbols
SYMSRV:  BYINDEX: 0x9
         c:\symbols*http://msdl.microsoft.com/download/symbols
         wntdll.pdb
         0D8A5E87C4E17D79C6BFE7DD265E0DD51
SYMSRV:  PATH: c:\symbols\wntdll.pdb\0D8A5E87C4E17D79C6BFE7DD265E0DD51\wntdll.pdb
SYMSRV:  RESULT: 0x00000000
DBGHELP: ntdll_775f0000 - public symbols  
        c:\symbols\wntdll.pdb\0D8A5E87C4E17D79C6BFE7DD265E0DD51\wntdll.pdb
SYMSRV:  BYINDEX: 0xA
         c:\symbols*http://msdl.microsoft.com/download/symbols
         wkernel32.pdb
         2A35F3BFB0D1413B80975BA3EF5B7BF81
SYMSRV:  PATH: c:\symbols\wkernel32.pdb\2A35F3BFB0D1413B80975BA3EF5B7BF81\wkernel32.pdb
SYMSRV:  RESULT: 0x00000000
DBGHELP: KERNEL32 - public symbols  
        c:\symbols\wkernel32.pdb\2A35F3BFB0D1413B80975BA3EF5B7BF81\wkernel32.pdb

User avatar
salvadordf
Posts: 4564
Joined: Thu Feb 02, 2017 12:24 pm
Location: Spain
Contact:

Re: Appcrash ChromeRuntime

Post by salvadordf »

You need to copy the PDB file to the symbols directory. Follow the instructions in this post :
https://www.briskbard.com/forum/viewtopic.php?t=1050

You also need to click on the "View" menu and then select "Call stack".

I just uploaded a video explaining how to debug errors in applications that include CEF browsers using WinDbg :
https://www.youtube.com/watch?v=ZYcqEbmoBZc

Enable the subtitles in that video.
win568neu
Posts: 29
Joined: Thu May 23, 2024 6:36 am

Re: Appcrash ChromeRuntime

Post by win568neu »

Hi Salvador

After weeks of testing, we have now found the reason for the app crash.
The problem did NOT occur when I started the application directly from the directory. Only when I called the application with a link or a remote application did our application crash in some cases.

Before initializing CEF, we had to call SETCURRENTDIR and set the directory to the current application. We had already set the SetCurrentDir property of GLOBALCEFAPP to TRUE, but that was tedious because the previous directory was restored when the call was exited. Tests have also shown that calling SETCURRENTDIR on a directory other than the application directory leads to an APPCRASH until the Chrome window is displayed for the FIRST TIME. From that point on, calling SETCURRENTDIR is no longer a problem.
Post Reply