Tesseract 4.0 segfault when using dictionary ces and psm 7

[nektor211]

Environment

• Tesseract Version:
  tesseract 4.00.00alpha
  leptonica-1.74.4
  libjpeg 8d (libjpeg-turbo 1.4.2) : libpng 1.2.54 : libtiff 4.0.6 : zlib 1.2.8

• Commit Number:
  2a77d5a - found after bisecting from current master

• Platform:
  Linux mc01 4.4.0-89-generic Warning in pixReadMemJpeg #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Current Behavior:

Segfault when running:

$tesseract bad.png - -l ces -psm 7
Warning. Invalid resolution 0 dpi. Using 70 instead.
contains_unichar_id(unichar_id):Error:Assert failed:in file ../ccutil/unicharset.h, line 513
Segmentation fault (core dumped)

Ces data were downloaded from https://github.com/tesseract-ocr/tessdata/raw/4.00/ces.traineddata .

Expected Behavior:

$ tesseract bad.png - -l ces -psm 7
Warning. Invalid resolution 0 dpi. Using 70 instead.
nguzge gbopf/IUMNIC CZ spol. s r.o.

Suggested Fix:

[amitdo]

What about other PSMs?

Ces data were downloaded from https://github.com/tesseract-ocr/tessdata/raw/4.00/ces.traineddata

There are newer traineddata files available.
https://github.com/tesseract-ocr/tesseract/wiki/Data-Files#updated-data-files-for-version-400-september-15-2017

[nektor211]

I cannot test it right now but I think that it worked ok when psm was not specified. I'll try to use the new data too, thanks.

[nektor211]

I've checked and new traineddata solved this issue.
As for what psm modes, the segfault appeared for modes 7, 8, 11 and 12 (also for 14- but those are probably not valid anyway).
I'm not sure wheter to close this issue right away, but my problem is now solved. Thank You.

[Shreeshrii]

Another reason for #293

Please give the URL link of the files which worked and which ones didn't?

Which --oem are you using with it?

[nektor211]

I've uploaded one that didn't work in the original post. One that works can be seen here:
. Otherwise it worked fine across a few thousand images, with only a single exception where it failed with the segfault mentioned above.

Oem was not set (as can be seen it examples above), so the default value.

[amitdo]

I suggest to close this issue since it was solved with an updated traineddata.

[IamDixit]

I had a similar issue.
Got it solved by taking a new training set from https://github.com/tesseract-ocr/tesseract/wiki/Data-Files#updated-data-files-for-version-400-september-15-2017