Andreas Lobinger

1. If you want them to be part of Cairo.jl just do a PR 2. Fonthandling/rendering is highly backend/system specific, what system are you testing? 3. Do i understand correctly,...

libcairo hands over the rendering of fonts to bitmaps (if needed) to another library, in most cases freetype, but 'system' font handling can be configured at compile or runtime. I...

@cormullion I'm not using the same or 'correct' terminology. Afaics MacOS claims not to read-in hinting information in the font. I used hinting as the process of grid-fitting.

I think it's because the surface type is used for all surfaces and the vector surfaces like SVG and PDF are created in Float64 dimensions (https://www.cairographics.org/manual/cairo-SVG-Surfaces.html#cairo-svg-surface-create)

Does storing Float64 introduce problems in your code?

Hmm, I lost track how we do things in julia today. Code looks reasonable and i think i have a local branch that does more or less the same, but...

I think i have seen something similar that lead to https://github.com/JuliaGraphics/Cairo.jl/pull/196 Just by looking at it i'd say that it's a mismatch of the libc/libc++ that was used to build...

How do you measure the memory usage (leak) and why are you sure, that's the surfaces?

A 512x512 ARGB surface should be around 1MB, so the 50M on windows shows already a reduction from your 20000 instances and the 2.7GB in linux might be the full...

As written above, I cannot test code right now and I would doubt, that libcairo has some inbuilt memory problems on linux systems. And the the same thing could be...