memory problem in v 5.3.3

[teowave]

I get these memory errors on documents that work fine with v4.7.3:

[13:33:02 WRN] [PdfProcessor.Docling] [batch] stderr: [info] Using docling default PDF backend (auto-selected): class=DoclingParseDocumentBackend, module=docling.backend.docling_parse_backend, docling-parse=5.3.3 {}
[13:33:02 INF] [PdfProcessor.Docling] [OK] 'redacted1.pdf' passed validation (size=2851361 bytes, ext=.pdf) {}
[13:33:02 WRN] [PdfProcessor.Docling] [batch] Processing 1 files... {}
[13:33:02 WRN] [PdfProcessor.Docling] [batch][progress] (1/1, 0%) starting: C:\demo\basedir1\redacted1.pdf {}
[13:33:02 WRN] [PdfProcessor.Docling] [batch][debug] Processing: input=C:\customer\redacted1.pdf {}
[13:33:02 WRN] [PdfProcessor.Docling] [batch][debug] ocr_root=C:\ocr\basedir1, rel_path=redacted1.pdf {}
[13:33:02 WRN] [PdfProcessor.Docling] [batch][debug] target_dir=C:\ocr\basedir1, base_stem=redacted1 {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [9]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [10]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [11]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [12]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [13]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [14]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [15]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [16]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [17]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [18]: std::bad_alloc {}
[13:33:02 INF] [PdfProcessor.Docling] [DatabaseLogger] LogFile status='processing' statusLower='processing' runGuid=300eb86c-e2da-4b1b-8624-c7d46fd0f2d4 {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [19]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [20]: std::bad_alloc {}
[13:33:02 INF] [PdfProcessor.Docling] [DatabaseLogger] STAMPING GUID for status 'processing' {}
[13:33:02 INF] [PdfProcessor.Docling] Updated processing log for: redacted1.pdf with status: processing {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [21]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [22]: std::bad_alloc {}
[13:33:02 WRN] [PdfProcessor.Docling] Stage preprocess failed for run 1, pages [23]: std::bad_alloc {}

the initial pages of the doc seem to be fine, but the bug sometimes triggers at page 6, sometimes at page 9 etc.

[teowave]

happens in the 5.4.0 version as well

[nikolica666]

i get error after like 100 pages in 5.3.

[hbiandri]

Same for me, is there any fix available? Did previous versions run without this error?

[PeterStaar-IBM]

@teowave Can you provide me a pdf example, want to quickly look into this!

[hbiandri]

https://www.astra.admin.ch/dam/astra/de/dokumente/standards_fuer_nationalstrassen/astra_13001_lueftungderstrassentunnel2008v203.pdf.download.pdf/astra_13001d.pdf&ved=2ahUKEwiv6YPJmIiTAxXu0gIHHdCzLegQFnoECAwQAQ&usg=AOvVaw2QyLC-Py9xj5QrvxxH_H-x

It is a swiss tunnel ventilation norm which leads to the exact same errors. Might help you. You can just google "ASTRA 13001 pdf" if you're afraid that it is a virus

[PeterStaar-IBM]

OK, just uploading the pdf here,

astra_13001d.pdf

@hbiandri Is there a particular page that is problematic

[hbiandri]

Stage preprocess failed for run 1, pages [50]: std::bad_alloc
Stage preprocess failed for run 1, pages [55]: std::bad_alloc
Stage preprocess failed for run 1, pages [58]: std::bad_alloc
Stage preprocess failed for run 1, pages [59]: std::bad_alloc
Stage preprocess failed for run 1, pages [61]: std::bad_alloc
Stage preprocess failed for run 1, pages [62]: std::bad_alloc
Stage preprocess failed for run 1, pages [72]: std::bad_alloc
Stage preprocess failed for run 1, pages [74]: std::bad_alloc

Sometimes it is less pages, tending to be more towards the end of the doc

[PeterStaar-IBM]

interesting, will have a good look!

[teowave]

Same for me, is there any fix available? Did previous versions run without this error?

docling-parse 4.7.3 runs fine, even on really big pdf docs that took 9h to process...

[PeterStaar-IBM]

@teowave @hbiandri With the latest docling-parse, I have no issue parsing the large documents (and 9h looks very weird).

What is your docling-parse version and your setup (CPU/GPU/RAM)?

[hbiandri]

I use docling-2.76.0
No GPU, 32GB of RAM and an Intel Ultracore 7. Not crazy specs but also not bad

[PeterStaar-IBM]

mmm, I see this,

taa@Munlochy docling % uv run docling --version
Docling version: 2.76.0
Docling Core version: 2.66.0
Docling IBM Models version: 3.11.0
Docling Parse version: 5.3.2
Python: cpython-312 (3.12.11)
Platform: macOS-26.2-arm64-arm-64bit

taa@Munlochy docling % time uv run docling --from pdf --to html /Users/taa/Downloads/astra_13001d.pdf

65.99s user 4.42s system 191% cpu 36.701 total

All works without errors. Could you run uv run docling --version?

[hbiandri]

Docling version: 2.76.0
Docling Core version: 2.66.0
Docling IBM Models version: 3.11.0
Docling Parse version: 5.4.0
Python: cpython-310 (3.10.11)
Platform: Windows-10-10.0.26200-SP0

[teowave]

@teowave @hbiandri With the latest docling-parse, I have no issue parsing the large documents (and 9h looks very weird).

What is your docling-parse version and your setup (CPU/GPU/RAM)?

for the 9h parsing: docling 2.73.1 docling-parse 4.7.3 (latest before 5) and 4x cpu, no gpu, 16 gb ram.

That being said, 9h was an outlier, I had over 4000 docs processed on that run, I had that one doc with 9h, about 1% with 2-3 hours , and the rest with times from a few seconds to a few tens of mins. So it is noth that all docs take 9h, it is only the big and complicated ones.

The version 5 chokes on some documents that work fine in 4.7.3, but it is after processing a few other documents. Then about half way through it displays the errors that I listed above. It then reports the document as processed, even though it is only half processed on examination, then it goes to the next document and chokes again about half way through and so on.