`segfault` with version `2.4.0` about freetype-py HOT 15 OPEN

It is just freetype.version(), according to the code:

from freetype-py.

I tried the patch proposed in #171 and the segfault still happens. Commenting out the Face.__del__ method also didn't fix it.

from freetype-py.

You do know 2.4.0 is about a decade old, right? I was adapting 2.6.x for the beginning of fontval, which was 2016, 7 years ago.

Edit: sorry , wasn't in touch with freetype-py version. In general, segfault is a freetype problem; strange exception is a freetype-py problem.

from freetype-py.

You do know 2.4.0 is about a decade old

I'm talking about freetype-py v2.4.0 which was release in May 4, 2023, not Python 2.4.0.

from freetype-py.

I think somebody else also updated the bundled freetype version recently, if you are using wheel or whatever it is called, rather than the system-wide freetype on most Linux machines.

from freetype-py.

I don't have freetype installed, and as I mentioned above, rolling back freetype-py to v2.3.0 no longer causes the segfault.
Is there a way to tell which version of freetype is bundled with each freetype-py?

from freetype-py.

Following the release notes of v2.4.0, I found this commit which updated freetype from 2.12.0 to 2.13.0.

from freetype-py.

You can query from within freetype-py - it is returned by FT_Version(), or something of similar name.

from freetype-py.

Some ways of installing freetype-py also build a bundled freetype. The version is controlled by
https://github.com/rougier/freetype-py/blob/master/setup-build-freetype.py so you might want to check that file's history. Regardless, putting something like FT_Version() inside your python code might be a better way of knowing what version of freetype you are using.

from freetype-py.

The crash only happens on macOS.

from freetype-py.