RenderBadPicture (invalid Picture parameter) error when using Xft rendering

[Jan Vrany]

When using Xft font rendering, after a while I'm getting following errors:

XWorkstation [error]: x-error caught maj=139 (0x8b) min=7 (0x7) resource=2c00423
XWorkstation [error]: x-error message is [143] 'RenderBadPicture (invalid Picture parameter)'
XWorkstation [error]: x-error caught maj=139 (0x8b) min=7 (0x7) resource=2c0043b
XWorkstation [error]: x-error message is [143] 'RenderBadPicture (invalid Picture parameter)'
DeviceWorkstation [info]: Display error: RenderBadPicture (invalid Picture parameter) in XRequest.139 - nil
DeviceWorkstation [info]: interrupting: an ioWait Process (event dispatcher (:0), id=5)
DeviceWorkstation [error]: Display error: RenderBadPicture (invalid Picture parameter) in XRequest.139
XWorkstation [error]: x-error caught maj=139 (0x8b) min=7 (0x7) resource=2c0016a
XWorkstation [error]: x-error message is [143] 'RenderBadPicture (invalid Picture parameter)'
VM [info] (14-01-04 17:19:26): error interrupt on unlimited stack - unwinding.
DeviceWorkstation [info]: Display error: RenderBadPicture (invalid Picture parameter) in XRequest.139 - nil
DeviceWorkstation [info]: interrupting: an ioWait Process (event dispatcher (:0), id=5)
DeviceWorkstation [error]: Display error: RenderBadPicture (invalid Picture parameter) in XRequest.139

So far no way how to reproduce. No visible artefacts, though.

[Jan Vrany]

Attached version of XftFontDescription uses per-view XftDraw and so far does not suffer from the RenderBadPicture problem. It exploits unused instvar in SimpleView.

Indeed it's very ugly hack. Also, it does not destroy XftDraw once the view is destroyed. But it shows that problem can be fixed by not sharing XftDraw.