Run paddleocr CPU on AWS cloud segmentation fault
See original GitHub issueDear author I tried run Paddle OCR on AWS cloud server. I got error Segmentation fault. I tried reinstall a lots of paddlepaddle-cpu versions. But It still not work, paddleocr ver 2.3.0.1, paddlepaddle ver 2.1.2. My output error:
— Running analysis [ir_graph_to_program_pass] I0910 09:50:52.969626 22710 analysis_predictor.cc:636] ======= optimize end ======= I0910 09:50:52.973817 22710 naive_executor.cc:98] — skip [feed], feed -> x I0910 09:50:52.976850 22710 naive_executor.cc:98] — skip [batch_norm_4.tmp_3], fetch -> fetch I0910 09:50:52.976873 22710 naive_executor.cc:98] — skip [conv2d_66.tmp_0], fetch -> fetch E0910 09:50:52.977479 22710 analysis_config.cc:81] Please compile with gpu to EnableGpu() — Fused 0 subgraphs into layer_norm op. (220, 1000, 3)
C++ Traceback (most recent call last):
0 paddle::framework::SignalHandle(char const*, int) 1 paddle::platform::GetCurrentTraceBackStringabi:cxx11
Error Message Summary:
FatalError: Segmentation fault is detected by the operating system.
[TimeInfo: *** Aborted at 1631267455 (unix time) try “date -d @1631267455” if you are using GNU date ***]
[SignalInfo: *** SIGSEGV (@0x0) received by PID 22710 (TID 0x7f4ac1bc3740) from PID 0 ***]
Segmentation fault (core dumped) Many thanks for any support
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
试一下cpu模式能不能跑 --use_gpu=false
Since you haven't replied for more than 3 months, we have closed this issue/pr. If the problem is not solved or there is a follow-up one, please reopen it at any time and we will continue to follow up. It is recommended to pull and try the latest code first. 由于您超过三个月未回复，我们将关闭这个issue/pr。 若问题未解决或有后续问题，请随时重新打开（建议先拉取最新代码进行尝试），我们会继续跟进。