Remove --output-type pdf from PDF OCR processing - #4
Merged
Merged
Conversation
This ran into a seeming bug in `ocrmypdf` where for some PowerPoint PDF exports, the OCR didn't succeed and instead ran into a seemingly infinite output of ```txt Recursion depth exceeded in _find_image_xrefs_page optimize.py:259 ``` This seems to be tracked in ocrmypdf/OCRmyPDF#1321, but for now has to be fixed by a workaround. This previously resulted in a RAM usage overload of the DMS, presumably because it tried to collect and log the (infinite) output logs of `ocrmypdf`. For internal discussions on this, cf. messages from "SysAdmin Int" from August 31st and September 1st 2026.
pklaschka
enabled auto-merge
September 1, 2026 09:45
pklaschka
disabled auto-merge
September 1, 2026 09:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This ran into a seeming bug in
ocrmypdfwhere for some PowerPoint PDF exports, the OCR didn't succeed and instead ran into a seemingly infinite output ofThis seems to be tracked in ocrmypdf/OCRmyPDF#1321, but for now has to be fixed by a workaround.
This previously resulted in a RAM usage overload of the DMS, presumably because it tried to collect and log the (infinite) output logs of
ocrmypdf. For internal discussions on this, cf. messages from "SysAdmin Int" from August 31st and September 1st 2026.main--output-type pdffrom PDF OCR processing 👈