[FIX] Handle NULL bitmap gracefully in OCR instead of crashing (#1010) #1878
+41
−17
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.
Summary
Root Cause
The code path was:
pixClipRectanglefails → "box outside rectangle" errorpixConvertRGBToGrayreceives NULL → "pixs not defined" errorcpix_gsis NULL, but code continues to line 415TessBaseAPIGetUTF8Textreturns NULL (no image was set)fatal()is called → crashFix
cpix_gs == NULLby cleaning up and returning NULL (skip bitmap)TessBaseAPIGetUTF8TextNULL case from fatal error to graceful skipTesting
This fix allows CCExtractor to continue processing even when individual subtitle frames are corrupted, which is critical for live streams where packet loss can occur.
Fixes #1010
🤖 Generated with Claude Code