Bug 146246 – [GTK] Empty gtk-font-name setting causes WebProcess crash rendering pages

• Status: RESOLVED
• Resolution: FIXED
• Component: WebKitGTK

Created attachment 255428 [details]
backtrace with symbols

On my Arch Linux x86_64 system, I don't have gconf/dconf/gnome-settings-daemon installed and have "gtk-font-name=" (with no value after the equals sign) under "[Settings]" in ~/.config/gtk-3.0/settings.ini. This configuration causes WebKit2's WebProcess to crash in WebCore::CSSParser::parseSystemFont with the attached backtrace, and prevents effectively all pages from being successfully rendered.

This occurs with both the packaged webkit2gtk 2.8.3-1 in the Arch repositories and with a freshly-built WebKit2GTK+ 2.8.3 from the same sources.

I debugged this in #webkitgtk+ IRC with mcatanzaro, who was able to reproduce by "[setting] org.gnome.desktop.font-name to an empty string with dconf-editor".

[Michael Catanzaro]

It's actually org.gnome.desktop.interface font-name (oops). Check the See Also for a somewhat better backtrace

decltype(nullptr)&& is probably my new favorite C++ type.

[Carlos Garcia Campos]

Created attachment 255473 [details]
Patch

[Michael Catanzaro]

(I'd been using the STABLE tag for crashes that affect the latest stable release; how do you prefer we use those?)

[Carlos Garcia Campos]

(In reply to comment #3)
> (I'd been using the STABLE tag for crashes that affect the latest stable
> release; how do you prefer we use those?)

I prefer is Stable is used for bugs that *only* affect stable releases. Bugs that are present in trunk and should be merged in stable branches, should be added to the stable wiki page to be merged in the branch once it lands in trunk.

[Carlos Garcia Campos]

Committed r185948: <http://trac.webkit.org/changeset/185948>