Bug 456925 - Bogus memory allocation size -- embedded pdf not shown/white page
Summary: Bogus memory allocation size -- embedded pdf not shown/white page
Status: RESOLVED UPSTREAM
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 22.04.3
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-19 16:33 UTC by Florian
Modified: 2022-08-03 22:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
pdf file not being displayed (358.08 KB, application/pdf)
2022-07-19 16:33 UTC, Florian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian 2022-07-19 16:33:28 UTC
Created attachment 150745 [details]
pdf file not being displayed

SUMMARY
I have a figure that is included in a pdf using LaTeX beamer. 
The figure is not shown in the presentation.
When openened directly the page is empty and also no content shown.
On the console opening the pdf directly or scrolling to the page where it is embedded yields 
'Bogus memory allocation size'

STEPS TO REPRODUCE
1. open the attached pdf

OBSERVED RESULT

a blank page is displayed, an error printed on the console

EXPECTED RESULT

showing the content of the pdf, like all other pdf viewers I tried to, e.g. xpdf, evince, even converting to png.

ADDITIONAL INFO

I am assuming this to be different from #404526 -- not building manually, using Arch, until now all other pdfs work just fine.

$ pdfinfo eco_middle.pdf
Producer:        cairo 1.16.0 (https://cairographics.org)
CreationDate:    Tue Feb  5 20:53:09 2019 CET
Custom Metadata: no
Metadata Stream: no
Tagged:          no
UserProperties:  no
Suspects:        no
Form:            none
JavaScript:      no
Pages:           1
Encrypted:       no
Page size:       720 x 405 pts
Page rot:        0
File size:       366672 bytes
Optimized:       no
PDF version:     1.5
Comment 1 Albert Astals Cid 2022-08-03 22:30:02 UTC
This is a poppler bug, please report it to https://gitlab.freedesktop.org/poppler/poppler/-/issues/new?issue