-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
segfault on pikepdf.open(bin_stream) for some pdf's #10
Comments
Thank you for this report. Any segfault is a serious concern. I can't reproduce it but I'm fairly sure it's a memory use-after-free issue and I might be able to solve it without reproducing it. But in the interest of reproducing, what platform are you on, and are you using pikepdf from a wheel or did you build a version? Regarding commercial support - contact me at jim@purplerock.ca and tell me a little about your project and requirements. |
IIRC I installed using pip. Platform:
Thank you for the info on commercial support. I'm still evaluating my options so no promises. I'll email you if I decide to go further in this direction. |
Should be fixed in v0.3.5/master... still can't reproduce, but I'm pretty sure I fixed it. |
Since you can't reproduce it, I just want to let you know that the fix works. Thanks a lot! |
Failed with segfault:
OK:
Other tests:
binary stream open (first snippet above) on tests/resources/pal-1bit-trivial.pdf -- OK (even though result is just a blank page)
my ebook collection |> "PathLike" open (second) snippet |> binary stream open snippet -- OK
my ebook collection |> binary stream open -- failed
my ebook collection |> various qpdf cli commands -- OK
On another note, the front page mentions "Commercial support is available" but I can't find any info about this anywhere. Do you have a pointer on this?
Thanks
The text was updated successfully, but these errors were encountered: