poppler issueshttps://gitlab.freedesktop.org/poppler/poppler/-/issues2024-02-11T13:19:42Zhttps://gitlab.freedesktop.org/poppler/poppler/-/issues/1456Render very slow and lag when opening pdf files created by powerpoint2024-02-11T13:19:42ZFirestar-ReimuRender very slow and lag when opening pdf files created by powerpointRender very slow and lag when opening pdf files created by powerpoint.
I find this issue when I open the slides[第17讲_总复习1.pdf](/uploads/8ba65cde102cd5647a6130ef4cce5404/第17讲_总复习1.pdf) written by my teacher which are 50-100 pages pdf fil...Render very slow and lag when opening pdf files created by powerpoint.
I find this issue when I open the slides[第17讲_总复习1.pdf](/uploads/8ba65cde102cd5647a6130ef4cce5404/第17讲_总复习1.pdf) written by my teacher which are 50-100 pages pdf files created by powerpoint.
I use okular and installed poppler-data
It usually needs several seconds to load a page or it will be blank, and it loads just 2-3 pages at one time.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1454Unicode supplementary plane support in annotation2024-01-15T16:48:47ZKeyu TaoUnicode supplementary plane support in annotationCurrently, poppler/Annot.cc still assumes each Unicode (UTF-16) character (scalar) takes 2 bytes. (https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/poppler/Annot.cc#L3042, https://gitlab.freedesktop.org/poppler/poppler/-/blob...Currently, poppler/Annot.cc still assumes each Unicode (UTF-16) character (scalar) takes 2 bytes. (https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/poppler/Annot.cc#L3042, https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/poppler/Annot.cc#L3048-3049)
This is true for BMP (Basic Multilingual Plane) characters. However, some characters like emoji and some rare characters in natural languages, are not in BMP and takes 4 bytes in UTF-16:
```console
>>> # use Python console as an example
>>> "a".encode(encoding="utf-16")[2:] # BOM stripped
b'a\x00'
>>> "😀".encode(encoding="utf-16")[2:]
b'=\xd8\x00\xde'
>>> "𰻝".encode(encoding="utf-16")[2:]
b'\x83\xd8\xdd\xde'
```
I have tried to add supplementary plane handling inside `HorizontalTextLayouter` constructor like this:
```diff
diff --git a/poppler/Annot.cc b/poppler/Annot.cc
index e8db39ff..8147d89f 100644
--- a/poppler/Annot.cc
+++ b/poppler/Annot.cc
@@ -3044,18 +3044,31 @@ public:
newFontNeeded = false;
} else {
Unicode uChar;
+ int charLength;
if (isUnicode) {
uChar = (unsigned char)(text->getChar(i)) << 8;
uChar += (unsigned char)(text->getChar(i + 1));
+ charLength = 2;
+ // If uChar is in supplementary plane, we need to get the next character
+ // because the font may not have the glyph for the first character.
+ if (uChar >= 0xD800 && uChar <= 0xDBFF) {
+ if (i + 3 < text->getLength()) {
+ uChar = (uChar - 0xD800) * 0x400 + ((unsigned char)(text->getChar(i + 2)) << 8) + (unsigned char)(text->getChar(i + 3)) + 0x10000;
+ charLength = 4;
+ printf("uChar: %x\n", uChar);
+ }
+ }
} else {
uChar = pdfDocEncoding[text->getChar(i) & 0xff];
+ charLength = 1;
}
const std::string auxFontName = form->getFallbackFontForChar(uChar, *font);
if (!auxFontName.empty()) {
+ printf("auxFontName: %s\n", auxFontName.c_str());
std::shared_ptr<GfxFont> auxFont = form->getDefaultResources()->lookupFont(auxFontName.c_str());
// Here we just layout one char, we don't know if the one afterwards can be layouted with the original font
- GooString auxContents = GooString(text->toStr().substr(i, isUnicode ? 2 : 1));
+ GooString auxContents = GooString(text->toStr().substr(i, charLength));
if (isUnicode) {
auxContents.prependUnicodeMarker();
}
@@ -3070,13 +3083,14 @@ public:
// we also need to allow the character if we have not layouted anything yet because otherwise we will end up in an infinite loop
// because it is assumed we at least layout one character
if (!availableWidth || *availableWidth > 0 || (isUnicode && i == 2) || (!isUnicode && i == 0)) {
- i += isUnicode ? 2 : 1;
+ i += charLength;
data.emplace_back(outputText.toStr(), auxFontName, blockWidth, charCount);
}
} else {
+ printf("auxFontName: not found\n");
error(errSyntaxError, -1, "HorizontalTextLayouter, couldn't find a font for character U+{0:04uX}", uChar);
newFontNeeded = false;
- i += isUnicode ? 2 : 1;
+ i += charLength;
}
}
// Now layout the rest of the text with the original font
```
However, this does not work (I'm testing this with Okular) as it could not find font to show the new uChar. I'm afraid that further investigation is a bit beyond my knowledge :(https://gitlab.freedesktop.org/poppler/poppler/-/issues/1453Text fails to display in Cairo backend but it's ok in Okular and Acrobat Reader2024-01-01T12:58:10ZNelson Benítez LeónText fails to display in Cairo backend but it's ok in Okular and Acrobat ReaderThe attached PDF (created by Acrobat Distiller 6.0 in Windows) shows fine in Okular and Acrobat Reader, but Evince and Poppler Cairo backend (pdftocairo) fails to display very large portions of text, it seems something related to the fon...The attached PDF (created by Acrobat Distiller 6.0 in Windows) shows fine in Okular and Acrobat Reader, but Evince and Poppler Cairo backend (pdftocairo) fails to display very large portions of text, it seems something related to the fonts embedded.
[bug168518.pdf](/uploads/e7ca4a22af14e4579caeedf6f9856899/bug168518.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1452pdfimages -png and -tiff give inverted colour output2023-12-30T14:09:36ZShriramana Sharmapdfimages -png and -tiff give inverted colour outputPlease download the attachment which is just the first page from https://archive.org/details/wg224 (to avoid huge download). This contains black text on white background.
Run the commands:
```
pdfimages -png p.pdf q
pdfimages -tiff p.p...Please download the attachment which is just the first page from https://archive.org/details/wg224 (to avoid huge download). This contains black text on white background.
Run the commands:
```
pdfimages -png p.pdf q
pdfimages -tiff p.pdf r
pdfimages -all p.pdf s
fax2tiff -o s-000.tif $(< s-000.params) s-000.ccitt
```
We can see that the files q-000.png and r-000.tif display the colours inverted ie white text on black background whereas going to CCITT and then to TIF gives the correct output.
Please look into this and fix it. Thank you!
Attachment:
[p.pdf](/uploads/5b253d8d62460aa22c9ac8a3d8b1d00a/p.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1451pdf to svg shows raster lines (clippaths)2024-01-02T16:14:59Zrvanderboompdf to svg shows raster lines (clippaths)Hey,
we like to use pdftocairo -svg for our pdf to svg conversion, but some material that exists of images concatted to 1 images via clippath , show raster lines where the seperate images connect.
Some other paid tools do not do this an...Hey,
we like to use pdftocairo -svg for our pdf to svg conversion, but some material that exists of images concatted to 1 images via clippath , show raster lines where the seperate images connect.
Some other paid tools do not do this and show as it is visible in pdf.
Added the materal and the svg result.
[HFD_20231216_0_005_HI.pdf](/uploads/e3e430b97bed774cf0519ec386875a4e/HFD_20231216_0_005_HI.pdf)
[HFD_20231216_0_005_HI.svg](/uploads/9a3a1197942d9fa55de206ec3a896d9b/HFD_20231216_0_005_HI.svg)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1450pdftocairo -pdf causes font errors that did not exist2023-12-14T22:24:28ZHakan Usaklipdftocairo -pdf causes font errors that did not existThe provided sample is a 1 page pdf without any errors in Adobe Acrobat.
[input.pdf](/uploads/e3ac808e1c5470a974e195224741cba6/input.pdf)
After processing on Windows with Poppler version 23.11.0
`pdftocairo.exe -pdf "c:\temp\input.pdf" ...The provided sample is a 1 page pdf without any errors in Adobe Acrobat.
[input.pdf](/uploads/e3ac808e1c5470a974e195224741cba6/input.pdf)
After processing on Windows with Poppler version 23.11.0
`pdftocairo.exe -pdf "c:\temp\input.pdf" "c:\temp\output.pdf"`
and checking the file in Adobe Acrobat, the following error message is introduced
![image](/uploads/1eeb6dc53c2d9d8fa93847e553fe49e6/image.png)
For your information and Best Regardshttps://gitlab.freedesktop.org/poppler/poppler/-/issues/1449Avoiding symbol clashes2024-02-12T23:28:33ZKai PastorAvoiding symbol clashesAn extended vcpkg CI run with paraview using vtk using gdal using poppler run into linker errors due `Parser::~Parser` being defined both in Paraview and in Poppler. This is just one class name to be concerned about. There is also Array,...An extended vcpkg CI run with paraview using vtk using gdal using poppler run into linker errors due `Parser::~Parser` being defined both in Paraview and in Poppler. This is just one class name to be concerned about. There is also Array, Dict, etc. What is the preferred solution:
- Moving the classes to a namespace, e.g. `Poppler`.
- Adding a prefix similar to `GooString`, i.e. `Goo...`.
- Adjust as needed vs. moving all private classes vs. moving all classes.
This will change ABI, and it won't be entirely source compatible. (It is possible to import the classes into the global namespace using `using ...`, but at least forward declarations must be changed. Macros might provide additional help, a la QT_BEGIN_NAMESPACE.)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1448[skia] FTBFS on Android with Fontconfig font manager2023-12-10T22:55:21ZJonLiu1993[skia] FTBFS on Android with Fontconfig font managerWhe I update port poppler version to [23.11.0](https://github.com/microsoft/vcpkg/pull/35494) I get this error:
````
CMakeFiles/poppler.dir/poppler/GlobalParams.cc.o -c /mnt/vcpkg-ci/buildtrees/poppler/src/er-23.11.0-08ca2759be.clean/pop...Whe I update port poppler version to [23.11.0](https://github.com/microsoft/vcpkg/pull/35494) I get this error:
````
CMakeFiles/poppler.dir/poppler/GlobalParams.cc.o -c /mnt/vcpkg-ci/buildtrees/poppler/src/er-23.11.0-08ca2759be.clean/poppler/GlobalParams.cc
/mnt/vcpkg-ci/buildtrees/poppler/src/er-23.11.0-08ca2759be.clean/poppler/GlobalParams.cc:1563:5: error: use of undeclared identifier 'displayFontDir'; did you mean 'displayFontDirs'?
displayFontDir = fontDir;
^~~~~~~~~~~~~~
displayFontDirs
/mnt/vcpkg-ci/buildtrees/poppler/src/er-23.11.0-08ca2759be.clean/poppler/GlobalParams.cc:1379:20: note: 'displayFontDirs' declared here
static const char *displayFontDirs[] = { "/usr/share/ghostscript/fonts", "/usr/local/share/ghostscript/fonts", "/usr/share/fonts/default/Type1", "/usr/share/fonts/default/ghostscript", "/usr/share/fonts/type1/gsfonts", nullptr };
^
/mnt/vcpkg-ci/buildtrees/poppler/src/er-23.11.0-08ca2759be.clean/poppler/GlobalParams.cc:1563:20: error: array type 'const char *[6]' is not assignable
displayFontDir = fontDir;
````
I see that displayFontDir is declared earlier in the file, so I don't know why I'm getting this error.
https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/poppler/GlobalParams.cc?ref_type=heads#L1278
````
// The path to the font directory. Set by GlobalParams::setFontDir()
static std::string displayFontDir;
````https://gitlab.freedesktop.org/poppler/poppler/-/issues/1447Poppler fails to open some password encrypted PDF which other readers can ope...2024-02-22T08:15:37ZNelson Benítez LeónPoppler fails to open some password encrypted PDF which other readers can open (after repairing)In this [downstream Evince issue](https://gitlab.gnome.org/GNOME/evince/-/issues/1889), a reporter mailed me a Password protected PDF document generated by his turkish online bank which he could not attach to gitlab as it contained perso...In this [downstream Evince issue](https://gitlab.gnome.org/GNOME/evince/-/issues/1889), a reporter mailed me a Password protected PDF document generated by his turkish online bank which he could not attach to gitlab as it contained personal data.
The PDF metadata shows it was created by `JasperReports Library version 6.9.0` and the PDF opens fine in Acrobat Reader, Firefox, and in `Xpdf 4.04`.
`Xpdf 4.04` shows the PDF had to be reconstructed to be opened, the Xpdf error window shows:
```
Syntax Error: Couldn't read xref table
Syntax Warning: PDF file is damaged -attempting to reconstruct xref table...
```
`Xpdf 4.04` is able to open this file because it has an updated "repairing code", my assumption comes from the fact that `Poppler`'s `XRef.cc` has the [comment shown below](https://gitlab.freedesktop.org/poppler/poppler/-/blob/poppler-23.06.0/poppler/XRef.cc#L857) while `XRef.cc` in `Xpdf 4.04` does not have that comment anymore, and the code seems refactored to support the aforementioned repairing from inside object streams.
```cpp
// Attempt to construct an xref table for a damaged file.
// Warning: Reconstruction of files where last XRef section is a stream
// or where some objects are defined inside an object stream is not yet supported.
// Existing data in XRef::entries may get corrupted if applied anyway.
bool XRef::constructXRef(bool *wasReconstructed, bool needCatalogDict)
{
//bla bla
}
```
We found where Firefox `PDF.js` fixed this same bug:
- https://github.com/mozilla/pdf.js/issues/15893
- https://github.com/mozilla/pdf.js/pull/15897
and good news they had a testcase pdf file which we could use publicly:
- [issue15893_reduced.pdf](/uploads/53917879af696462740484498756021d/issue15893_reduced.pdf) password is `test`
Anyway, I'm sure our Evince user Sabri Ünal would mail privatly the bank PDF file to any Poppler developer interested in trying that too.
------------
So, I went ahead and took the time to locate the involved Xpdf 4.04 code and migrate it to Poppler, with sucessful results in opening the problematic password encrypted files. I'll be sending MR's.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1446Font selection (okular)2023-12-13T22:39:32ZAlbert WikFont selection (okular)I'm using poppler as part of the okular application, and I'm having problems getting it to select the right fonts.
To reproduce the issue, download and open the following PDF:
https://gwern.net/doc/psychology/personality/psychopathy/194...I'm using poppler as part of the okular application, and I'm having problems getting it to select the right fonts.
To reproduce the issue, download and open the following PDF:
https://gwern.net/doc/psychology/personality/psychopathy/1941-cleckley-maskofsanity.pdf
Note: make sure you have the relevant fonts installed.
Here is a screenshot from okular:
https://drive.google.com/file/d/178nuOFvWiBOoqmSIs7spAqDrGt2YHAqQ/view
The fonts "CourierNew" and "TimesNewRoman" are installed on the system, but poppler substitutes "NimbusMonoPS" and "Times Roman".
fontconfig appears to be correctly configured:
```
$ fc-match "CourierNew"
cour.ttf: "Courier New" "Regular"
$ fc-match "TimesNewRoman"
times.ttf: "Times New Roman" "Regular"
```https://gitlab.freedesktop.org/poppler/poppler/-/issues/1445'Symbol' font on Windows not found2023-12-10T22:38:46ZHakan Usakli'Symbol' font on Windows not foundAfter updating poppler to version 23.11 on Windows an issue started happening that seems to be documented but I am still unsure how to deal with it properly. I would appreciate any help.
Older versions of poppler did not complain about ...After updating poppler to version 23.11 on Windows an issue started happening that seems to be documented but I am still unsure how to deal with it properly. I would appreciate any help.
Older versions of poppler did not complain about this: Syntax Error: No display font for 'Symbol' when using
`pdffonts -subst input.pdf `
or
`pdftocairo.exe -pdf input.pdf output.pdf`
What I checked and tried so far:
-File 'symbol.ttf' is available in Windows/Fonts directory. Copying it into the binary folder of the poppler executable makes no difference.
-I have read Issue #1174 - Invalid mathematical (cryptographic) symbols rendered in some PDF's (needs symbol.ttf) but that issue is on Linux, not Windows.
The Changelog from Version 23.06 reads:
```
Windows: Look for fonts in both windows font dir and poppler fonts dir
Windows: symbol.ttf is not a good Symbol font
```
I did not understand why 'symbol.ttf' is not considered a good symbol font. Windows users use it because it comes with the system.
My question: what is the recommended way on Windows systems, starting with release 23.06 and higher so that symbol.ttf is not reported as a syntax error or missing. Would an entry in a configuration file help to point poppler to the symbol.ttf file ? How would that config file need to look like and where does it need to be placed. A sample would be appreciated.
If required I can supply a sample file that is looking for 'symbol'
Best Regards
PS:
I am upgrading from version 21.11 and there is significant performance improvement on some files for pdfcairo -pdf (rewriting pdfs). Processing speed is much faster. Great work.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1444Undeprecate `poppler_document_new_from_data` and fix its API.2023-11-18T11:50:01ZFabian KeßlerUndeprecate `poppler_document_new_from_data` and fix its API.Poppler is not used only from C, when using poppler from C++ or rust, the memory is mostly managed indirectly via containers.
Passing data from a C++ container is now very cumbersome.
This on top also applies to data from a memory mapped...Poppler is not used only from C, when using poppler from C++ or rust, the memory is mostly managed indirectly via containers.
Passing data from a C++ container is now very cumbersome.
This on top also applies to data from a memory mapped file.
Therefore, I propose to undeprecate it and to fix its API to something like this:
```
PopplerDocument *
poppler_document_new_from_data (const char *data,
ptrdiff_t length,
const char *password,
GError **error);
```https://gitlab.freedesktop.org/poppler/poppler/-/issues/1443PDF generated of a webpage by Safari renders with a fault, but Firefox and Ap...2023-11-14T19:24:30ZRoland CheePDF generated of a webpage by Safari renders with a fault, but Firefox and Apple's Preview displays correctly.I used Safari's print dialog's PDF option to print a [website](https://apple.stackexchange.com/questions/435946/how-can-i-point-gcc-and-g-to-the-gnu-compiler-collection) to PDF.
Zathura 0.5.2 (Girara 0.4.0) with pdf-poppler plugin (0.3....I used Safari's print dialog's PDF option to print a [website](https://apple.stackexchange.com/questions/435946/how-can-i-point-gcc-and-g-to-the-gnu-compiler-collection) to PDF.
Zathura 0.5.2 (Girara 0.4.0) with pdf-poppler plugin (0.3.0), does not show "Ask Different", instead, it shows "Ask D".
![Screen_Shot_2023-11-12_at_1.59.32_pm](/uploads/da809285d668be7f71e8d7f2daa1e2dd/Screen_Shot_2023-11-12_at_1.59.32_pm.png)
Both Apple's Preview and Firefox PDF viewer shows "Ask Different" correctly.[Ask_Different_-_Safari_Print_PDF.pdf](/uploads/32c5f35d855260b2f50dc60a00a60239/Ask_Different_-_Safari_Print_PDF.pdf)
After this, I used Firefox's print dialog to save a PDF of the same website. The generated PDF looks different but "Ask Different" can be seen correctly in all: Apple's Preview, Firefox's PDF viewer, and Zathura.
Whatever is the problem with the Safari-generated PDF, I hope Poppler will render the correct image just like firefox did.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1442PDF incorrectly cropped when converted to eps with pdftocairo2023-10-12T22:21:36ZMarkus JohnssonPDF incorrectly cropped when converted to eps with pdftocairoThe content gets incorrectly cropped when converting this pdf to eps using pdftocairo.
Instead of the expected size (as per pdfinfo) of `563.04 x 450 pts` I get (with whatever parameters I try) this cropped bounding box: `%%BoundingBox:...The content gets incorrectly cropped when converting this pdf to eps using pdftocairo.
Instead of the expected size (as per pdfinfo) of `563.04 x 450 pts` I get (with whatever parameters I try) this cropped bounding box: `%%BoundingBox: 7 137 450 551` in the eps file.
SVG, png and jpeg all works fine. (svg: ` width="563.03998" height="450" viewBox="0 0 563.03998 450"`)
[example.pdf](/uploads/2772d4a29be466addc3494685e020139/example.pdf)
[output.eps](/uploads/885f37c40713bcf68a61e592db73bc24/output.eps)
I'm using Poppler 23.10.0 on Macos. I got the same result with 23.08.0 on Windows. And 22.02.0 on linux mint.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1441/poppler/CairoOutputDev.cc:1943: Segmentation fault2023-10-24T12:58:31Z刘文/poppler/CairoOutputDev.cc:1943: Segmentation faultversion:23.09.0
My system OS:Ubuntu 20.04<br>
reproduce:pdftocairo -png poc.pdf output.png<br>
The stack information is as follows:<br>
Program received signal SIGSEGV, Segmentation fault.<br>
0x000000000041f8cd in CairoOutputDev::setS...version:23.09.0
My system OS:Ubuntu 20.04<br>
reproduce:pdftocairo -png poc.pdf output.png<br>
The stack information is as follows:<br>
Program received signal SIGSEGV, Segmentation fault.<br>
0x000000000041f8cd in CairoOutputDev::setSoftMask (this=0x67a500, state=<optimized out>, bbox=<optimized out>, alpha=<optimized out>, transferFunc=
0x6ad970, backdropColor=<optimized out>) at /Oscar01/liujiahao/poppler-master/poppler/CairoOutputDev.cc:1943
1943 source_data[y * stride + x] = lum << 24;
(gdb) bt<br>
#0 0x000000000041f8cd in CairoOutputDev::setSoftMask (this=0x67a500, state=<optimized out>, bbox=<optimized out>, alpha=<optimized out>,
transferFunc=0x6ad970, backdropColor=<optimized out>) at /Oscar01/liujiahao/poppler-master/poppler/CairoOutputDev.cc:1943<br>
#1 0x00007ffff7a848b1 in Gfx::doSoftMask (this=this@entry=0x68aab0, str=<optimized out>, str@entry=0x7fffffffdbd0, alpha=<optimized out>,
blendingColorSpace=0x0, isolated=<optimized out>, knockout=<optimized out>, transferFunc=<optimized out>, backdropColor=<optimized out>)
at /Oscar01/liujiahao/poppler-master/poppler/Gfx.cc:1289<br>
#2 0x00007ffff7a7a9af in Gfx::opSetExtGState (this=0x68aab0, args=0x7fffffffdd70, numArgs=<optimized out>)
at /Oscar01/liujiahao/poppler-master/poppler/Gfx.cc:1161<br>
#3 0x00007ffff7a82a70 in Gfx::go (this=this@entry=0x68aab0, topLevel=false) at /Oscar01/liujiahao/poppler-master/poppler/Gfx.cc:685<br>
#4 0x00007ffff7a82508 in Gfx::display (this=this@entry=0x68aab0, obj=0x7fffffffe238, obj@entry=0x3ff0000000000000, topLevel=false)
at /Oscar01/liujiahao/poppler-master/poppler/Gfx.cc:646<br>
#5 0x00007ffff7a84ebd in Gfx::drawForm (this=0x68aab0, str=0x3ff0000000000000, resDict=<optimized out>, matrix=<optimized out>, bbox=0x7fffffffe1c0,
transpGroup=<optimized out>, softMask=<optimized out>, blendingColorSpace=0x0,
isolated=<error reading variable: That operation is not available on integers of more than 8 bytes.>,
knockout=<error reading variable: That operation is not available on integers of more than 8 bytes.>, alpha=false, transferFunc=0x0,
backdropColor=0x0) at /Oscar01/liujiahao/poppler-master/poppler/Gfx.cc:4836<br>
#6 0x00007ffff7a94714 in Gfx::doForm (this=this@entry=0x68aab0, str=0x1, str@entry=0x7fffffffe238)
at /Oscar01/liujiahao/poppler-master/poppler/Gfx.cc:4766<br>
#7 0x00007ffff7a7225d in Gfx::opXObject (this=0x68aab0, args=<optimized out>, numArgs=<optimized out>)
at /Oscar01/liujiahao/poppler-master/poppler/Gfx.cc:4139<br>
#8 0x00007ffff7a82a70 in Gfx::go (this=this@entry=0x68aab0, topLevel=false) at /Oscar01/liujiahao/poppler-master/poppler/Gfx.cc:685<br>
#9 0x00007ffff7a82508 in Gfx::display (this=0x68aab0, obj=0x7fffffffe5e8, topLevel=true) at /Oscar01/liujiahao/poppler-master/poppler/Gfx.cc:646<br>
#10 0x00007ffff7b33d19 in Page::displaySlice (this=0x67dd00, out=<optimized out>, hDPI=<optimized out>, vDPI=<optimized out>, rotate=<optimized out>,
useMediaBox=<optimized out>, crop=<optimized out>, sliceX=<optimized out>, sliceY=<optimized out>, sliceW=<optimized out>, sliceH=<optimized out>,
printing=<optimized out>, abortCheckCbk=<optimized out>, abortCheckCbkData=<optimized out>, annotDisplayDecideCbk=<optimized out>,
annotDisplayDecideCbkData=<optimized out>, copyXRef=<optimized out>) at /Oscar01/liujiahao/poppler-master/poppler/Page.cc:584<br>
#11 0x00007ffff7b3cef8 in PDFDoc::displayPageSlice (this=<optimized out>, out=0x67a500, page=<optimized out>, hDPI=<optimized out>,
vDPI=<optimized out>, rotate=<optimized out>, useMediaBox=true, crop=false, printing=<optimized out>, sliceX=<optimized out>,
sliceY=<optimized out>, sliceW=<optimized out>, sliceH=<optimized out>, abortCheckCbk=<optimized out>, abortCheckCbkData=<optimized out>,
annotDisplayDecideCbk=<optimized out>, annotDisplayDecideCbkData=<optimized out>, copyXRef=<optimized out>)
at /Oscar01/liujiahao/poppler-master/poppler/PDFDoc.cc:633<br>
#12 0x000000000040ec1a in renderPage (doc=0x67d970, cairoOut=0x67a500, pg=1, page_w=612, page_h=792, output_w=<optimized out>, output_h=<optimized out>)
at /Oscar01/liujiahao/poppler-master/utils/pdftocairo.cc:705<br>
#13 main (argc=<optimized out>, argv=<optimized out>) at /Oscar01/liujiahao/poppler-master/utils/pdftocairo.cc:1243<br>
[poc.pdf](/uploads/22594304907875d1112122a5fd53b5e9/poc.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1440pdfseparate poc.pdf output-%d.pdf:run out of all memory2023-10-07T05:32:32Z刘文pdfseparate poc.pdf output-%d.pdf:run out of all memoryversion:23.09.0
My system OS:Ubuntu 20.04
reproduce: pdfseparate poc.pdf output-%d.pdf
When I executed this test case, I ran out of over 200G of memory,I don't know if this is caused by a memory leak or other issue.[poc.pdf](/uploads/...version:23.09.0
My system OS:Ubuntu 20.04
reproduce: pdfseparate poc.pdf output-%d.pdf
When I executed this test case, I ran out of over 200G of memory,I don't know if this is caused by a memory leak or other issue.[poc.pdf](/uploads/d3d4cf8b52fc6a87250e0fdf32f373bf/poc.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1439Poppler 23.09 and Qt 6.5.2 - #include "poppler-export.h" <--- File not found.2023-09-27T11:21:46ZOnevoidPoppler 23.09 and Qt 6.5.2 - #include "poppler-export.h" <--- File not found.While trying to build **Poppler 23.09** on **Qt 6.5.2**, there's the following critical error in **qt6/src/poppler-annotation.h**, line #45.
**#include "poppler-export.h"** <--- File not found.
This critical file **"poppler-export.h"...While trying to build **Poppler 23.09** on **Qt 6.5.2**, there's the following critical error in **qt6/src/poppler-annotation.h**, line #45.
**#include "poppler-export.h"** <--- File not found.
This critical file **"poppler-export.h"** is nowhere to be found in the Poppler file system structure.
Thanks in advance.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1438Poppler-23.09.0 fails to build on Solaris2023-10-02T07:15:26ZMartin ŘehákPoppler-23.09.0 fails to build on Solarispoppler-23.09.0 fails to build with following error on Solaris:
```
[ 48%] Linking CXX shared library libpoppler.so
ld: fatal: option --version-script requires option -z gnu-version-script-compat to be specified
collect2: error: ld retur...poppler-23.09.0 fails to build with following error on Solaris:
```
[ 48%] Linking CXX shared library libpoppler.so
ld: fatal: option --version-script requires option -z gnu-version-script-compat to be specified
collect2: error: ld returned 1 exit status
```
CMakeLists.txt contains this:
```
if(UNIX AND (NOT APPLE))
set_target_properties(poppler PROPERTIES LINK_OPTIONS LINKER:--version-script=${LINKER_SCRIPT})
endif()
```
I tried to use `-z gnu-version-script-compat` as suggested, but it is failing with following error:
```
[ 64%] Linking CXX executable pdfseparate
Undefined first referenced
symbol in file
__iob CMakeFiles/pdfseparate.dir/parseargs.cc.o (symbol belongs to unavailable version ../libpoppler.so.131.0.0 ((null)))
ld: fatal: symbol referencing errors
collect2: error: ld returned 1 exit status
```
To be honest I don't understand the latter issue at all, so the only way I was able to workaround that was to ifdef it this way:
```
-if(UNIX AND (NOT APPLE))
+if(UNIX AND (NOT APPLE AND NOT CMAKE_HOST_SOLARIS))
```
Solaris has specific ld which tries to be compatible with GNU ld, but for some reason doesn't behave in the same way here.
Is this linker setting important or is it just fine to merge the change above to make it build, please?
Thank you,
Martinhttps://gitlab.freedesktop.org/poppler/poppler/-/issues/1437Pdftoppm "Bogus memory allocation size" with high resolution raster2023-09-22T11:53:57ZFrancisnei Bernardes LimaPdftoppm "Bogus memory allocation size" with high resolution rasterUsing Poppler v22.12.0 on Debian Debian GNU/Linux 12 (bookworm)
The following command will error with "Bogus memory allocation size":
pdftoppm -r 500 ~/pdftoppm_bogus_memory_allocation_size.pdf /tmp/bogus_mem
But decreasing the resolut...Using Poppler v22.12.0 on Debian Debian GNU/Linux 12 (bookworm)
The following command will error with "Bogus memory allocation size":
pdftoppm -r 500 ~/pdftoppm_bogus_memory_allocation_size.pdf /tmp/bogus_mem
But decreasing the resolution from 500 to 150, the command will complete correctly.
The pdf file is confidential, but I can send it to the interested developer.
Thank you very much!https://gitlab.freedesktop.org/poppler/poppler/-/issues/1436Too big png and jpg are not displayed2023-10-22T15:00:36ZRiccardo GagliarducciToo big png and jpg are not displayedSome files, a pdf with embedded graphic and the exported images (pdfimages -j ...), does not display.
They can be opened in Gimp and partially Krita without problems.
The source is public Italian cartography.
Files are quite big so here...Some files, a pdf with embedded graphic and the exported images (pdfimages -j ...), does not display.
They can be opened in Gimp and partially Krita without problems.
The source is public Italian cartography.
Files are quite big so here a WeTransfer link: https://we.tl/t-kokvgUrNME
Thank you,
Riccardo