michael@0: diff --git a/gfx/cairo/cairo/src/cairo-gstate.c b/gfx/cairo/cairo/src/cairo-gstate.c
michael@0: --- a/gfx/cairo/cairo/src/cairo-gstate.c
michael@0: +++ b/gfx/cairo/cairo/src/cairo-gstate.c
michael@0: @@ -1841,16 +1841,17 @@ _cairo_gstate_show_text_glyphs (cairo_gs
michael@0:  							transformed_glyphs,
michael@0:  							&num_glyphs,
michael@0:  							transformed_clusters);
michael@0:  
michael@0:      if (status || num_glyphs == 0)
michael@0:  	goto CLEANUP_GLYPHS;
michael@0:  
michael@0:      _cairo_gstate_copy_transformed_source (gstate, &source_pattern.base);
michael@0: +    _cairo_clip_init(&clip);
michael@0:  
michael@0:      /* For really huge font sizes, we can just do path;fill instead of
michael@0:       * show_glyphs, as show_glyphs would put excess pressure on the cache,
michael@0:       * not all components below us correctly handle huge font sizes, and
michael@0:       * path filling can be cheaper since parts of glyphs are likely to be
michael@0:       * clipped out.  256 seems like a good limit.  But alas, seems like cairo's
michael@0:       * rasterizer is something like ten times slower than freetype's for huge
michael@0:       * sizes.  So, no win just yet when we're using cairo's rasterizer.