<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Patch] Skip XRef gaps in PDFDoc save methods"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107057">107057</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[Patch] Skip XRef gaps in PDFDoc save methods
</td>
</tr>
<tr>
<th>Product</th>
<td>poppler
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>poppler-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>haxtibal@posteo.de
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=140372" name="attach_140372" title="Skip XRef xrefEntryNone entries on incremental update and full rewrite">attachment 140372</a> <a href="attachment.cgi?id=140372&action=edit" title="Skip XRef xrefEntryNone entries on incremental update and full rewrite">[details]</a></span> <a href='page.cgi?id=splinter.html&bug=107057&attachment=140372'>[review]</a>
Skip XRef xrefEntryNone entries on incremental update and full rewrite
This patch aims to solve Okular bug
<a href="https://bugs.kde.org/show_bug.cgi?id=395660">https://bugs.kde.org/show_bug.cgi?id=395660</a>. Actually there are several related
problems, the patch fixes the easiest and sufficient part.
Currently, PDFDoc::saveIncrementalUpdate and saveCompleteRewrite iterate over
the full continuous range of XRef::entries, ranging from object id 0 up to
XRef::size. That seems problematic. The range may contain gaps (type ==
xrefEntryNone) which are merely details of popplers memory allocation, but
don't contain objects from the PDF document. Hitting a gap with XRef::getEntry
triggers "damaged file repair". It's implemented by XRef::constructXRef, and it
makes things actually worse because constructXRef can't handle XRef streams nor
objects from inside object streams. It wipes out formerly existing XRef
information in that case.
The idea of this patch is to spare the gaps from iteration, and therefore avoid
a bunch of consecutive faults early.
Atm. the patch is only tested for Okular test case. Poppler regression tests
are yet outstanding.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>