-
Notifications
You must be signed in to change notification settings - Fork 352
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
Segmentation fault during processing #42
Comments
Please give the pdf file link. |
@mmartinello I know that there are (segfault) problems if you are using "non-standard" fonts... as I did not realize that while I had updated pdf2htmlEX for poppler, that I had not done the same for fontforge. I have now tooled up to attempt the fontforge work, unfortunately this might take some time (the initial poppler work certainly did). However, as @starryfu suggests, it would be very helpful to have a copy of your PDF file (as it must be using fonts that trigger pdf2htmlEX's use of fontforge). Without your PDF file I will not be able to verify that I have found the fontforge related problems. (This issue will be related to #41 -- though in issue #41 the problems were detected at compile time rather than run time). |
Hi. Im also having a segmentation fault. I have uploaded the pdf file here: https://gofile.io/?c=lONa9b If iI use the --split-pages 1 option it works fine until the page 139/156, then crashes.
|
Many thanks for uploading your PDF. I have just tested it using my development server on ubuntu 19.10, and I have no problems. I can see from the pdf2htmlEX version information, that you have recently recompiled libfontforge, can you tell me which version of the sources you are using? Could you also let me know which underlying operating system you are using? |
I have the same problem for font. I have tested it both on MacOS and docker in CentOS7.
And I use lldb :
I have uploaded the pdf file here :https://we.tl/t-tiBbvvGSqF |
So, Im using it with this fontforge version: https://github.com/fontforge/fontforge/releases/tag/20190413 I can confirm this only happens with the version of pdf2htmlEx and fontforge that I posted, i have tried it in another machine with this version, and it doesnt break
Thing is, I had this old version in both machines, then decided to upgrade one of them to version 0.18.7 and poppler 0.81 to see if it would work. Its worked mostly fine, its only this PDF so far thats giving me trouble |
@GMolini (and @guoxuequan ) SO.. the pdf2htmlEX sources have not (yet) been updated to use any fontforge after tag/20170731 (which most Ubuntu releases are still using). I am, at the moment, exploring how to release pdf2htmlEX as both an AppImage and a Docker image so that pdf2htmlEX can use the more recent fontforge and poppler releases on older distributions. Once I have done that, I will then update the pdf2htmlEX sources to use the most recent poppler and fontforge (stable) releases. Alas this might take me a couple of weeks. I know that with the current fontforge, whether or not a given PDF succeeds or segFaults is very hit-or-miss. It depends entirely on the fonts embedded in the PDF. I would suggest trying to work on an Ubuntu 18.04 OS with the older deb that I released until I can get AppImage and Docker images working. (@guoxuequan I have put your PDF into my collection of examples and will have a look at it as soon as I can). |
Thanks. I have made a docker on Ubuntu 19.10 with the pdf2htmlex_0.18.6-1.git20190927r583b1-0ubuntu1.disco1_amd64.deb. It run well for my PDF. This is my docker https://hub.docker.com/repository/docker/guoxuequan/pdf2htmlex |
We found that if the pdf content have a difference punctuation, for example , a string most of Chinese characters but only one English punctuation, it will catch exception and exit. |
pdf2htmlEX version 0.18.7, installed on Debian Stretch with poppler 0.81.0 compiled.
I'm receiving "segmentation fault" when I try to process a PDF file:
The text was updated successfully, but these errors were encountered: