Bug 99778 - Drawing failure with large MediaBox
Summary: Drawing failure with large MediaBox
Status: RESOLVED INVALID
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-12 14:02 UTC by Guillaume Endignoux
Modified: 2018-04-17 09:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Drawing failure (541 bytes, application/pdf)
2017-02-12 14:02 UTC, Guillaume Endignoux
Details

Description Guillaume Endignoux 2017-02-12 14:02:41 UTC
Created attachment 129520 [details]
Drawing failure

If a document contains pages with large differences in page size (/MediaBox field), drawing failure occurs. Attached is an example with two empty pages, the first one has dimensions 100000x100000 and the second one has dimensions 10x10. Upon opening with Evince, the window does not display properly and the following appears on stderr.


(evince:14359): Gtk-WARNING **: drawing failure for widget `EvView': invalid matrix (not invertible)
(evince:14359): Gtk-WARNING **: drawing failure for widget `GtkScrolledWindow': invalid matrix (not invertible)
(evince:14359): Gtk-WARNING **: drawing failure for widget `GtkOverlay': invalid matrix (not invertible)
(evince:14359): Gtk-WARNING **: drawing failure for widget `GtkBox': invalid matrix (not invertible)
(evince:14359): Gtk-WARNING **: drawing failure for widget `GtkPaned': invalid matrix (not invertible)
(evince:14359): Gtk-WARNING **: drawing failure for widget `GtkBox': invalid matrix (not invertible)
(evince:14359): Gtk-WARNING **: drawing failure for widget `EvWindow': invalid matrix (not invertible)
Comment 1 Albert Astals Cid 2017-02-13 18:51:59 UTC
Why is this a poppler bug and not an evince bug?
Comment 2 Guillaume Endignoux 2017-02-16 22:26:54 UTC
The same document seems to affect pdftoppm, which reports a "Bogus memory allocation size" on stderr, but prints weird stuff on stdout...

$ pdftoppm file.pdf
Bogus memory allocation size
P6
1 1
255
���P6
21 21
255
...

$ pdftoppm file.pdf > /dev/null
Bogus memory allocation size

$ pdftoppm file.pdf 2> /dev/null
P6
1 1
255
���P6
21 21
255
...
Comment 3 Albert Astals Cid 2017-02-16 23:03:30 UTC
pdftoppm can't render that file at default resolution because it'd have to allocate too much memory.

Try with -r 10


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.