Acrobat 9 crashes on OCR

[John_L....@adobeforums.com]

I've been trying to convert a batch of large PDF files to PDF searchable files by using the OCR of Acrobat. In the middle of a batch, a large (1000+ page) document crashes acrobat. I have narrowed it down to this image:

<http://img90.imageshack.us/img90/2418/badke2.png>
59,520 bytes

When I convert it to PDF (File->Create PDF->From Single File) and then use Acrobat to "Document->OCR Text Recognize->Recognize Text using OCR", Acrobat always crashes.

Is this true for anyone else that could try it?

It kills my batch processing and is making this large conversion quite painful. Is there a way around it?

[Bill@VT]

The basic problem is that the png file is a 172 X 172 resolution. The minimum is 200dpi. I tried it in AA5 and it warned of an invalid resolution. I switched it to 2X the resolution. At that the OCR ran, but the only conversion was on the page number. I have no idea why AA9 would have crashed, but it is likely related to the page resolution.

[John_L....@adobeforums.com]

Every other page in these documents are the same dpi so I don't think that is the issue.

Here is a two page PDF with a different page that crashes Acrobat 9:

<http://rapidshare.com/files/152486163/TwoPages.pdf.html>

Acrobat 9 crashes when I try to OCR page 2, but works well on page 1. They are both the same DPI as far as I can tell.

It would be nice if someone with AA9 could confirm this.

[Mark_...@adobeforums.com]

Not sure this is right place for this question, but...
Is there a "one-step" way to highlight all the occurences of a particular word in an OCR'd pdf? I currently find the 1st occurrence and highlight it, then find the next occurrence and highlight it, then find the next occurrence and highlight it, and so on...but surely there is an automated way to do this....

[michaelkazlow]

Mark,

This thread relates to crashes with OCR. Your post does not. Please
start your own thread. Don't hijack unrelated threads.

Mike

[Olga_S...@adobeforums.com]

I have problem to download first file that caused crash :
<http://img90.imageshack.us/img90/2418/badke2.png>

Could you, please send it to me as attachment to osat...@adobe.com.

Thanks,
Olga

[John_L....@adobeforums.com]

I have sent the email with the attachment.

[Olga_S...@adobeforums.com]

I was able to reproduce crash in both cases. Fix will be available in the next dot release of Acrobat - 9.1.
Thanks for your help!

Olga Satchouk,
Acrobat QE

[John_L....@adobeforums.com]

Thank you. I hope it is released soon as I have 6 more cases where it crashes during OCR. Perhaps they are all related to this common cause that you have already fixed.

Here are the current 8 pages that crash Acrobat 9 during OCR in a single PDF if you can test:

<http://rapidshare.com/files/154734045/CrashPages.pdf.html>

[Olga_S...@adobeforums.com]

Yes, it looks like the same problem on all pages caused crash in Acrobat 9.0. All pages came out just fine after OCR with 9.1.

Thanks again for your help.

[Captai...@adobeforums.com]

when is the new adobe 9.1 coming out then?

[Doug...@adobeforums.com]

Does anyone have information on the release of 9.1 or the fix to this issue?

Thanks

[Whitt_...@adobeforums.com]

My boss and I do document digitizing and we are having the same problem. Not every file crashes, only random larger files. I was wondering if anyone else had any insight on fixing this.

Thanks.

[kraz...@adobeforums.com]

I am having the same problem with 40 + pages to ocr.

[Aurora_...@adobeforums.com]

Does anyone know when the 9.1 version will be available? I'm having these same frustrating OCR problems!

[DN_Oc...@adobeforums.com]

Yes; I have the same problem with 9.0 Pro:

When I try to OCR a .pdf document to perform searches, it always crashes with the following error:

AppName: acrobat.exe AppVer: 9.0.0.332 ModName: ocrlibraryinf.dll

ModVer: 2.0.0.1 Offset: 000206f1

[Pete_D...@adobeforums.com]

Same problem; using Acrobat 9 on three stations and Acrobat 8 on one station. Acrobat 9 has failed to complete a batch OCR on ANY station while Adobe 8 has yet to fail, and it has done several large batches.
Any help yet? I have 60,000 pages to OCR.

[Steven_...@adobeforums.com]

Same problem here. Just purchased 9.0 for a project and am having this problem with over a thousand documents. ocrlibraryinf.dll.
When will 9.1 be available?!

For those of you who only have a few pdf's to ocr, try extracting the culprit pages as tif, then importing them back in. It worked for me, but I cant do that for 1000+ documents.

[Daniel_...@adobeforums.com]

We have had the same problem and provided samples to Jason Reuer at Adobe. His e-mail address is jre...@adobe.com. This is very frustrating. We tried purchasing the extended version of Acrobat Pro 9 and it has the same problem as does Adobe 8.1. Since I was unable to get any response back from Jason Reuer, I tried communicating with Olga Satchouk at Adobe who responded here. Her e-mail address is no longer valid.

Does anyone have any idea how to get around this problem now, or when the mystery version 9.1 that supposedly corrects it will be released. Acrobat is useless to our organization with this mission critical bug and it is frustrating that Adbobe has not been more responsive.

Also, does anyone have the e-mail address of someone higher up at Adobe so that we can elevate this issue, or at least let them know of Adobe's failure to repsond to all our requests.

[Terry_...@adobeforums.com]

I also encountered same problem, using AA8.1.3, against 63 very large (600megs+) PDF files that were created with a utility that did not make them searchable.

I also found that AA8 crashed during running OCR. Huge shortcoming.... AA8 does everything in memory, stores nothing in temporary files, forgets everything it did upon crashing, forces a mammoth time consuming restart from the beginning.

I finally got through them all by breaking each file into 2 files (a and b), then running OCR 100 pages at a time within each file, with constant attention.

A random error message, "Cannot find file" keept popping up, stopping, waits for me to click on "OK", adding to huge delays. Gotta constantly watch for this error. Even though I click on "Ignore this message", it does not listen, keeps popping up.

But at least, as it successfully gets through 100 pages, I can save it, then carry on to next 100 pages. If it crashes, I can restart to the last successful 100 pages completed.

I conclude that AA8 absolutely hates large files. My computer is a 2.6Ghz DualCore with 3.5 megs of memory, still not enough memory.
Took me an entire week to work my way through these 63 files, which BTW, tied up my computer for that whole time, insufficient memory to do other things.

That AA8 does not work with temporary files is a huge shortcoming when working with large PDF files. I find it astonishing that upon an unexpected failure, it has no way to remember where it was when the crash occured.

This situation begs the question...... Is there any other utility out there that will make a PDF file searchable, that is not made searchable when first created by some utility other than Acrobat?

Regards,

Terry Smythe
Winnipeg, Canada
smy...@shaw.ca

[Daniel_...@adobeforums.com]

No. The problem is not just big files - although the problems are worse in that case. I tried OCR on a 1600 page TIFF. Acrobat would crash with no indication of where it encountered a problem and all OCR done to that point was lost. I split the document into 100 page sections to identify the source of the crash. 4 of the 100 page sections bombed. I then did OCR on each of the four by splitting them into single pages. I identified four pages of the 1600 that were causing the crash. OCR on those single pages crashed Adobe on multiple machines running every possible setting. I provided the pages to Jason Reuer at Adobe (jre...@adobe.com) at his request and heard nothing back despite multiple e-mails. So much for customer service. I am able to perform OCR on these pages using OmniPage Pro 1.5 with no problem, so it is not the pages. I also provided Adobe with pages from other documents that produce crashes. Again, I heard no response. In this forum, Adobe claims that the problems are fixed in Acrobat 9.1, but they have not responded to any of our requests about how to get Acrobat 9.1. If anyone knows, please tell the rest of us.

Adobe batch handing capability compounds the problem. Instead of loading, performing OCR and saving one document at a time, it tries loading them all at once into memory. I am trying to perform OCR on 100,000 small documents, so that method is a disaster. One crash and everything is lost. As everyone has noted - a crash is certain, so Acrobat is basically useless in its current state for OCR. This has been true for Acrobat 7, 8 and 9.

This is all vetry frustrating.

[Terry_...@adobeforums.com]

On 5 Jan 2009 at 2:37, Daniel E. Smith wrote:

I am able to perform OCR on these pages using OmniPage Pro 1.5 with no
problem, so it is not the pages.

Agreed. In every case, where AA8 crashed, I was able to have AA8 run OCR against the offending page as if nothing was wrong, then carry on. Very mysterious, and extremely aggravating.

But the big question..... Is there another utility out there that will run OCR in such a way that the PDF file becomes searchable thereafter?

I have no trouble running OCR from any number of OCR packages, and all work just fine, but the OCR results are always external to the PDF file. The PDF file remains non-searchable even after running it with ABBYY, OmniPagePro, TextBridge, ScanSoft, etc.

So far, AA7 or better is the only utility I have found that when OCR is run, it leaves behind a PDF file that is searchable.

This is important in the case of a very large set of very large PDF files initially created by some utility other than Acrobat. 100% of these PDF files are not searchable.

In my case, some 50,000+ pages of a historical newspaper, 1881 to 1943, were scanned into TIFF format by some automated process, likely using an ADF. Then the TIFF files were converted by some automated utility into PDF files, all non-searchable.

I want to concatenate the TIFF files by year, then convert these yearly files into yearly PDF files. But such a process leaves them all non-searchable.

I've basically done this by using AA8, but the process was incredibly time consuming and aggravating, requiring constant attention for all these dumb repetitive errors that keep popping up, ignoring my earlier selection to ignore all errors. GGrrrrr..................... Urge to kill........... :-)

Regards,

Terry

[Terry_...@adobeforums.com]

Olga Satchouk says:

I was able to reproduce crash in both cases. Fix will be available in
the next dot release of Acrobat - 9.1.

How about the same fix for AA8.1.3, for those of us volunteers who can't afford the high cost of version 9? We don't have a company budget to fall back on, even though the work we are doing clearly benefits society as a whole.

[v...@adobeforums.com]

Rather than breaking the PDF into smaller files, run OCR until it crashes, note the page, then run OCR up to the page before the crash. Then run OCR again starting the page AFTER the crash.

At least you'll have the PDF doc in one piece, even though certain pages in the doc won't have been OCR'd.

Then you can insert re-scanned pages into the appropriate spot.

This was a workaround that worked for me.

[Terry_...@adobeforums.com]

Thank you for your suggestion. I did try that, but discovered that AA8 would sometimes crash on an earlier page, forcing restart again at the beginning. I concluded that as AA8 does everything in memory, that these 600meg PDF files were simply too big. And even on a swift 3.0Ghz dual-core system with 3.5 gigs of memory, it still took a huge amount of time.

Curiously, If I took note of the offending page where it crashed, AA8 would OCR process the 10 pages embracing the offending page, quite normally, if I sent it to process just those pages.

As a consequence, rather than trust it to crash at same spot, I elected to break the files in half, then OCR process 100 pages at a time, saving the file at conclusion of each group. It might still crash occasionally, but at least I did not have to repeat what had already been done successfully.

Knitting the broken files together after successful OCR processing is really quite trivial, done in seconds, not a hardship.

But how nice it would be if the fix applied to Version 9 would also be applied to version 8.1.3. As a volunteer, I can't afford version 9, and my version 8.1.3 otherwise does the job, albeit with aggravation.

When the next big group of similar PDF files emerge, I won't waste so much time experimenting. I'll just repeat this process from the beginning.

Regards, and thank you for thinking of me, appreciated.

Terry Smythe

[Christop...@adobeforums.com]

I'm also having problems with Acrobat crashing randomly when OCRing large scanned documents (>100MB). These problems began with Acrobat 8 and are still there in AA9!

What kind of fix do you mean Adobe has applied to AA9? Since installing the boxed version, Adobe's Update application never found any updates for AA9 :-(

[Christop...@adobeforums.com]

So I guess the latest stable version for doing OCR is Acrobat 7, isn't it?

[Gerry_H...@adobeforums.com]

Version 3 was awesome, simple and stable. Came with an office scanner.
Version 5.05 was great, everything in one package, before Acrobat split standard and pro.
Version 6.X was a nightmare with bloated PDFs and snails performance. Luckily I just had to help others who had it.
Version 7.1 Pro was/is easy and stable.
Version 8.x I have no personal experience with.
Version 9 Pro Extended trial has some really nice features like one-step watermark removal, but have not bought the upgrade yet. Its good to hear other people's trials and tribulations, even though you would hardly ever have positive posts, thanking Adobe for a great product.

[Christop...@adobeforums.com]

Adobe released the Acrobat 9.1 update yesterday. Unfortunately, the online updater doesn't find it so you have to download it manually from Adobe's website.

As far as I can tell the OCR engine is much more stable now! No more crashes so far...