Hi All, I have a latest Webkit Windows build (WebKit-r59711) with Coregraphics/Cfnetwork. It builds fine. When I run it using the command debug-safari , then it crashes on launch. Always crashes in WebCore__FontCache__getLastResortFallbackFont(). Seems like its not able to crate a CGFont. Request to let know If I have missed something with respect to Font. Crash dump : user.dmp. *----> System Information <----* Number of Processors: 2 Processor Type: x86 Family 6 Model 15 Stepping 11 Windows Version: 5.1 Current Build: 2600 Service Pack: 3 Current Type: Multiprocessor Free *----> State Dump for Thread Id 0x1c28 <----* eax=0000005e ebx=054d2470 ecx=781421d1 edx=781c3c70 esi=0012e65c edi=0012e8e0 eip=02cbd41b esp=0012e65c ebp=0012e8e0 iopl=0 nv up ei pl nz na po nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000206 function: WebKit!WebCore__FontCache__getLastResortFallbackFont 02cbd3fa 0074058b add [ebp+eax-0x75],dh 02cbd3fe 45 inc ebp 02cbd3ff f4 hlt 02cbd400 eb3a jmp WebKit!WebCore__FontCache__getLastResortFallbackFont+0x34c (02cbd43c) 02cbd402 6a00 push 0x0 02cbd404 68f00a2304 push 0x4230af0 02cbd409 686c010000 push 0x16c 02cbd40e 68200b2304 push 0x4230b20 02cbd413 e860166dff call WebKit!WTFReportAssertionFailure (0238ea78) 02cbd418 83c410 add esp,0x10 FAULT ->02cbd41b c705efbeadbb00000000 mov dword ptr [bbadbeef],0x0 ds:0023:bbadbeef=???????? 02cbd425 33c0 xor eax,eax 02cbd427 8bf4 mov esi,esp 02cbd429 ffd0 call eax 02cbd42b 3bf4 cmp esi,esp 02cbd42d e82eaa2800 call WebKit!_RTC_CheckEsp (02f47e60) 02cbd432 33c9 xor ecx,ecx 02cbd434 75e5 jnz WebKit!WebCore__FontCache__getLastResortFallbackFont+0x32b (02cbd41b) 02cbd436 33d2 xor edx,edx 02cbd438 75c8 jnz WebKit!WebCore__FontCache__getLastResortFallbackFont+0x312 (02cbd402) 02cbd43a 33c0 xor eax,eax *----> Stack Back Trace <----* 0012e8e0 0261d46d 0012ea1c 0012eaa0 cccccccc WebKit!WebCore__FontCache__getLastResortFallbackFont+0x32b 0012e914 02544d01 0012ea1c 0554852c 00000000 WebKit!WebCore__FontCache__getFontData+0x1ad 0012e948 022b880c 0012ea1c 00000000 055484d0 WebKit!WebCore__FontFallbackList__fontDataAt+0x111 0012e95c 022b8781 0012ea1c 0012eaa0 cccccccc WebKit!WebCore__FontFallbackList__primaryFontData+0x1c 0012e974 022b86d2 0012ea1c 0012eaa0 0012ea1c WebKit!WebCore__FontFallbackList__primarySimpleFontData+0x71 0012e988 025438ff cccccccc 0012ea1c 0012e9d8 WebKit!WebCore__Font__primaryFont+0x72 0012e998 0282e894 0012e9b4 00000000 00000000 WebKit!WebCore__Font__floatWidth+0x1f 0012e9d8 0282ea42 0012ea1c 05540a0c 00000004 WebKit!WebCore__stringWidth+0x54 0012e9f0 02829102 0012ea18 0012ea1c 00000000 WebKit!WebCore__StringTruncator__width+0x22 0012ea04 02368bbd 0012ea18 0012ea1c 02168bd8 WebKit!WebCore__WebCoreTextFloatWidth+0x12 0012ea4c 010afb10 0554844c 00000004 0012eaa0 WebKit!TextFloatWidth+0x3d 05587670 00000000 0550fe40 00000000 00000000 Safari+0x1fb10 Thanks & Regards, Deepak Sherveghar
What version of Safari do you have installed?
Safari Version : 4.0.3(531.9.1)
Hi Adam, I installed latest version of safari [4.0.5(531.22.7)] on my machine. Now everything is working fine. I am able to debug as well. Thank you so much for all the help and support. Request to let know, what base version of safari is generally required for a windows build with apple libraries. Also would be interested in knowing as to why it used to crash with 4.0.3 version of safari. Thanks and hoping for a reply.
Marking resolved per the above comments.
(In reply to comment #3) > I installed latest version of safari [4.0.5(531.22.7)] on my machine. > Now everything is working fine. I am able to debug as well. I'm glad it's working again. > Request to let know, what base version of safari is generally required for a windows build with apple libraries. Also would be interested in knowing as to why it used to crash with 4.0.3 version of safari. We make no attempt to keep WebKit nightly builds working with any but the latest release of Safari. There are periods of time where older releases will still work, but there's never any guarantee. We do this so that WebKit's code doesn't become filled with hard-to-maintain and hard-to-test backward-compatibility code.