Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

free type memory leak #3276

Closed
tacaswell opened this issue Jul 18, 2014 · 3 comments
Closed

free type memory leak #3276

tacaswell opened this issue Jul 18, 2014 · 3 comments
Assignees
Milestone

Comments

@tacaswell
Copy link
Member

via @neothemachine

Seems to be something else:

==19165== 188,736 (187,648 direct, 1,088 indirect) bytes in 5,864 blocks are definitely lost in loss record 2,253 of 2,307
==19165==    at 0x4C27AAA: malloc (vg_replace_malloc.c:291)
==19165==    by 0x1565342B: FT2Font::make_open_args(_object*, FT_Open_Args_*) (ft2font.cpp:2191)
==19165==    by 0x15667125: FT2Font::FT2Font(Py::PythonClassInstance*, Py::Tuple&, Py::Dict&) (ft2font.cpp:869)
==19165==    by 0x1566BC2C: Py::PythonClass<FT2Font>::extension_object_init(_object*, _object*, _object*) (ExtensionType.hxx:273)
==19165==    by 0x4ED9857: type_call (typeobject.c:745)
==19165==    by 0x4E769A2: PyObject_Call (abstract.c:2529)
==19165==    by 0x4F254CC: PyEval_EvalFrameEx (ceval.c:4239)
==19165==    by 0x4F27B7D: PyEval_EvalCodeEx (ceval.c:3253)
==19165==    by 0x4F25D29: PyEval_EvalFrameEx (ceval.c:4117)
==19165==    by 0x4F27B7D: PyEval_EvalCodeEx (ceval.c:3253)
==19165==    by 0x4F25D29: PyEval_EvalFrameEx (ceval.c:4117)
==19165==    by 0x4F27B7D: PyEval_EvalCodeEx (ceval.c:3253)
@letmaik
Copy link
Contributor

letmaik commented Jul 18, 2014

Don't look into that further for the moment. It may have been a fault on my side with the installation (which I didn't do myself) where just the leak-patch (from #3274) was taken and not the full branch of yours (which seems to contain a ft leak patch as well since rc1)

@letmaik
Copy link
Contributor

letmaik commented Jul 18, 2014

Ok, there's no new leak. Sorry for the confusion. The issue is invalid and can be closed.

@mdboom
Copy link
Member

mdboom commented Jul 18, 2014

I think this was fixed very recently by #3256.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants