Søren Sandmann <[email protected]> writes:

> diff --git a/fb/fbscreen.c b/fb/fbscreen.c
> index 7c7d656..f9080a4 100644
> --- a/fb/fbscreen.c
> +++ b/fb/fbscreen.c
> @@ -32,6 +32,7 @@ fbCloseScreen(ScreenPtr pScreen)
>      int d;
>      DepthPtr depths = pScreen->allowedDepths;
>  
> +    fbDestroyGlyphCache();
>      for (d = 0; d < pScreen->numDepths; d++)
>          free(depths[d].vids);
>      free(depths);

You got me there for a second -- you'll destroy the glyph cache every
time a screen gets closed, which (now) happens on hot un-plug.

But, it's all OK -- the glyph cache will be re-created the next time
glyphs are painted, and anything else would be a whole lot more trouble
to track.

Reviewed-by: Keith Packard <[email protected]>

-- 
[email protected]

Attachment: pgpBELiHtMqjz.pgp
Description: PGP signature

_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to