JaidedAI / EasyOCR

Ready-to-use OCR with 80+ supported languages and all popular writing scripts including Latin, Chinese, Arabic, Devanagari, Cyrillic and etc.
https://www.jaided.ai
Apache License 2.0
24.42k stars 3.16k forks source link

Illegal instruction (core dumped) #1174

Open sura2k opened 11 months ago

sura2k commented 11 months ago

Error: Illegal instruction (core dumped) Environment: Ubuntu 22.04 (VirtualBox, Windows Host) Python 3.10.12 EasyOCR 1.7.1 Virtual Env using Poetry

This worked about a week ago and suddenly the same script giving this error without installing any other dependencies.

I tested this again in a new Ubuntu 22.04 virtual box instance and now issue is still there permanently.

shaimarus commented 9 months ago

I have same issue on CPU, also I try use their dockerfile, still same error https://github.com/JaidedAI/EasyOCR/blob/master/Dockerfile But it works on GPU

symmetrically commented 9 months ago

I am also facing the same problem with easyocr 1.7.1:

easyocr -l en -f test.jpg --gpu=False
Neither CUDA nor MPS are available - defaulting to CPU. Note: This module is much faster with a GPU.
[W NNPACK.cpp:64] Could not initialize NNPACK! Reason: Unsupported hardware.
Illegal instruction (core dumped)

Here are my machine specs:

rchitecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         36 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  8
  On-line CPU(s) list:   0-7
Vendor ID:               GenuineIntel
  Model name:            Intel(R) Xeon(R) CPU E31230 @ 3.20GHz
    CPU family:          6
    Model:               42
    Thread(s) per core:  2
    Core(s) per socket:  4
    Socket(s):           1
    Stepping:            7
    CPU max MHz:         3600.0000
    CPU min MHz:         1600.0000
    BogoMIPS:            6385.95
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
                         a cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht 
                         tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon p
                         ebs bts rep_good nopl xtopology nonstop_tsc cpuid aperf
                         mperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est t
                         m2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcn
                         t tsc_deadline_timer aes xsave avx lahf_lm pti ssbd ibr
                         s ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsav
                         eopt dtherm ida arat pln pts md_clear flush_l1d
Virtualization features: 
  Virtualization:        VT-x
Caches (sum of all):     
  L1d:                   128 KiB (4 instances)
  L1i:                   128 KiB (4 instances)
  L2:                    1 MiB (4 instances)
  L3:                    8 MiB (1 instance)
NUMA:                    
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-7
Vulnerabilities:         
  Gather data sampling:  Not affected
  Itlb multihit:         KVM: Mitigation: VMX disabled
  L1tf:                  Mitigation; PTE Inversion; VMX conditional cache flushe
                         s, SMT vulnerable
  Mds:                   Mitigation; Clear CPU buffers; SMT vulnerable
  Meltdown:              Mitigation; PTI
  Mmio stale data:       Unknown: No mitigations
  Retbleed:              Not affected
  Spec rstack overflow:  Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
                          and seccomp
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer
                          sanitization
  Spectre v2:            Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIB
                         P conditional, RSB filling, PBRSB-eIBRS Not affected
  Srbds:                 Not affected
  Tsx async abort:       Not affected

Any help in solving this issue would be appreciated. Thanks

ardakshalkar commented 6 months ago

Same issue, who knows how to solve it?

minyukim commented 6 months ago

Have you ever tried downgrading torch? I got the same message and EasyOCR didn't work, but after downgrading the torch it works fine, even though the message still appear.

The version I'm using now: