FS#52606 - [fontforge] Crash when building Iosevka font

Attached to Project: Arch Linux
Opened by Jurica Vukadin (u-ra) - Tuesday, 17 January 2017, 22:39 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 28 January 2017, 20:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
100% reproducible crash when building Iosevka font. Full error log in attachment.

Additional info:
* package version(s)
python 3.6.0-2
fontforge 20161012-3

Steps to reproduce:

pacaur -S fontforge npm otfcc ttfautohint
git clone https://github.com/be5invis/Iosevka
cd Iosevka
npm install
make
...
*** Error in `fontforge': free(): invalid size: 0x00007f351636ded0 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x70c4b)[0x7f3521c86c4b]
/usr/lib/libc.so.6(+0x76fe6)[0x7f3521c8cfe6]
/usr/lib/libc.so.6(+0x777de)[0x7f3521c8d7de]
/usr/lib/libfontforge.so.2(+0x1cb6cd)[0x7f35212bf6cd]
/usr/lib/libpython3.6m.so.1.0(_PyCFunction_FastCallDict+0x8f)[0x7f351d17191f]
/usr/lib/libpython3.6m.so.1.0(+0x168a0f)[0x7f351d180a0f]
/usr/lib/libpython3.6m.so.1.0(_PyEval_EvalFrameDefault+0x317)[0x7f351d13cd77]
/usr/lib/libpython3.6m.so.1.0(PyEval_EvalCodeEx+0x277)[0x7f351d180f47]
/usr/lib/libpython3.6m.so.1.0(PyEval_EvalCode+0x1b)[0x7f351d13ca5b]
/usr/lib/libpython3.6m.so.1.0(+0x1eddc2)[0x7f351d205dc2]
/usr/lib/libpython3.6m.so.1.0(PyRun_FileExFlags+0x9d)[0x7f351d20862d]
/usr/lib/libpython3.6m.so.1.0(PyRun_SimpleFileExFlags+0x1a7)[0x7f351d208817]
/usr/lib/libpython3.6m.so.1.0(Py_Main+0x6b1)[0x7f351d1fd6f1]
/usr/lib/libfontforge.so.2(PyFF_Main+0xd2)[0x7f35212c14c2]
/usr/lib/libfontforge.so.2(CheckIsScript+0x306)[0x7f35212e3b46]
/usr/lib/libfontforgeexe.so.2(fontforge_main+0x2e7)[0x7f3522391317]
/usr/lib/libc.so.6(__libc_start_main+0xf1)[0x7f3521c36291]
fontforge(_start+0x2a)[0x40067a]
   fontforge.log (37 KiB)
This task depends upon

Closed by  Gaetan Bisson (vesath)
Saturday, 28 January 2017, 20:07 GMT
Reason for closing:  Upstream
Comment by Gaetan Bisson (vesath) - Tuesday, 24 January 2017, 07:09 GMT
That's very strange. Could you see if rebuilding fontforge fixes this issue? Otherwise please report it upstream. It really does not look like a packaging problem to me. Cheers.
Comment by Jurica Vukadin (u-ra) - Wednesday, 25 January 2017, 13:12 GMT
Yes, this is an upstream problem. I managed to reproduce it with manually building the latest git checkout.

Loading...