When creating and destroying toy font faces concurrently on multiple threads, sometimes an assertion is raised:
/build/buildd/cairo-1.12.14/src/cairo-hash.c:506: _cairo_hash_table_lookup_exact_key: Assertion `!"reached"' failed.
I first observed this in Mono:
I asked about it on the mailing list and someone confirmed that it occurs even in a trivial C program:
I think this is the sequence of events:
Thread A runs cairo_toy_font_face_create to create a font. It completes normally and is added to cairo_toy_font_face_hash_table.
Thread A decrefs the font face. Its refcount drops to 0, and _cairo_toy_font_face_destroy will run, except--
Thread B runs cairo_toy_font_face_create to create the same font. It is found in the hash table, a reference is added, and it is returned.
Thread B decrefs the font face. Its refcount drops to 0.
Thread B runs _cairo_toy_font_face_destroy.
Thread B acquires the lock on the hash table, confirms that the refcount is still 0, then removes the hash table entry, releases the lock and goes on to deallocate the font.
Thead A wakes up and continues running _cairo_toy_font_face_destroy. It acquires the lock on the hash table, and - uh-oh! - it confirms that the refcount is still 0. It is! (I think this was potentially an access-after-free, too.) Thread A tries to remove the font from the hash table, and asserts.
Author: Chris Wilson <email@example.com>
Date: Tue Sep 17 16:28:19 2013 +0100
font: Push the last reference dec into the backend->destroy() callback
In order to close a race between locking the backend and resurrecting a
font via the cache, we need to keep the font face alive until after we
take the backend lock. Once we have that lock, we can drop our reference
and test if that was the last. Otherwise we must abort the destroy().
This fixes the double-free exposed by multithreaded applications trying
to create and destroy the same font concurrently.
Reported-by: Weeble <firstname.lastname@example.org>
Signed-off-by: Chris Wilson <email@example.com>