Created attachment 270753 [details]
Crash report for WebKitWebProcess
Running MiniBrowser on a source build of WebKitGTK+ 2.10.7 on OS X 10.11 causes WebKitWebProcess to crash.
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libwebkit2gtk-4.0.37.dylib 0x0000000107eea634 WebCore::FontCache::lastResortFallbackFont(WebCore::FontDescription const&) + 148
1 libwebkit2gtk-4.0.37.dylib 0x0000000107590824 WebCore::CSSFontFaceSource::font(WebCore::FontDescription const&, bool, bool, WebCore::CSSFontSelector*) + 596
2 libwebkit2gtk-4.0.37.dylib 0x000000010758f6bf WebCore::CSSFontFace::font(WebCore::FontDescription const&, bool, bool) + 255
Can you disassemble WebCore::FontCache::lastResortFallbackFont, so we can see what is going on at that point?
Sure, I'm quite new to this sort of stuff, how would I go about doing that?
Could this be related to bug 141432, it seems similar but it's pretty a ancient bug.
It has to be at least related, because that function is pretty simple.
I guess you have a problem with fontconfig, such that it cannot find any serif font. Crashing is the right thing to do in that case, but we should still handle it better
Fixed it! Reinstalling fontconfig with the configure option:
fixed it (credit to the maintainer of the fontconfig MacPorts port).
Can you please reopen this to add an informative release assertion here instead of crashing?
Sure, how would I do that?
See bug #141432
*** This bug has been marked as a duplicate of bug 141432 ***