-
Notifications
You must be signed in to change notification settings - Fork 83
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
Out of memory on surface finish #239
Comments
Everything is working with these builds: |
Got exactly the same thing. Windows 10 64-bit, Python 3.9.1, pycairo 1.21.0. import cairo
with cairo.PDFSurface("test.pdf", 200, 200) as surface:
cairo.Context(surface).show_page() Basically pycairo is unusable for me here. |
Worked with the build found here, many thanks (this .whl collection has saved my skin quite a few times before). But the PyPI version remains entirely useless. |
@eleroy you're a champ. This solution really just saved me hours worth of headaches. |
Yeah, I can reproduce the error. On the packages version of Cairo on PyPI, I found the Cairo version bundled to be >>> import cairo
>>> cairo.cairo_version()
11702 and on the wheel from https://www.lfd.uci.edu/~gohlke/pythonlibs/#pycairo, it's >>> import cairo
>>> cairo.cairo_version()
11600 So it must be something with the version of the library used. Also, the most recent version is 1.17.6 (developmental release) and I'll try and see if I can reproduce it there. I should also work on #243 someday. >>> import cairo
>>> cairo.cairo_version()
11706
>>> surface = cairo.PDFSurface("example.pdf", 200, 200)
>>> surface.finish() |
I can reproduce the issue with 1.22.0, but with 1.23.0, which includes the new cairo build everything seems to work now. So I think this is fixed in the latest release. |
I assumed this was fixed in cairo then. |
In python 3.8, windows 10 x64, pycairo 1.20.1:
The call with the context manager works, but the last line surface finish throws an out of memory error. This is now only possible to use the surface within the context manager for some reason ?
Does anyone have the same issue ?
Thank you
The text was updated successfully, but these errors were encountered: