🚀 go-pugleaf

While I'm at it, this one has had me worried for _AGES_.

In my program, I open a font. I close it and quit. Memory counter drops
a bit. No deal. Flush fonts. No memory loss. Fair enough. After I run
the program, the font sits in memory, and takes up space. It is available
for use if I want to open the font again.

I run my program, quit. Counter goes down, Run it again, counter
goes down again by the same amount. The counter goes down by the same amount
_every_ time I run the program. Flush fonts, all memory back again.
SO: each time I run the program, I get a _new_ copy of the font in memory.
This copy doesn't come from disk (no access), it is copied from one
part of memory to another. 

I checked this out with Xoper. Sure enough, every time I run the program,
a new font is created in memory, exactly the same size and specs as the
others, and after quitting they all have 0 processes using then on the 
counter.

This is pretty bad, but when you consider that my program opens _four_
fonts, it is getting rediculous.

QUESTIONS: Is this a bug? Is there a special way of asking for fonts that
actually lets you use the one already there? Is there any salvation in
2.0?

Regards Alan