-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PaddleOCR throwing fscanf failed #12138
Comments
First, it is recommended to verify that the PaddlePaddle framework is successfully installed. import paddle
paddle.utils.run_check()
# PaddlePaddle is installed successfully! Then, please provide the smallest reproducible demo. |
Please provide the most basic operating environment so that we can reproduce this error locally and make the necessary modifications? OS: If you only provide error information without providing context, we cannot solve it here! Because we don't know in what environment this error was reported. |
I have uninstalled paddlepaddleocr. |
W0517 10:10:58.219796 252 default_variables.cpp:95] Fail to fscanf: Success [0]
By any chance, does it have some relevance with Core Dumped , asking because when I was using the latest version of paddlepaddle-gpu, I was constantly hitting this error inside the docker:
`root@f76833e33ee6:/code/build/data# python3 paddle_and_annotate.py
C++ Traceback (most recent call last):
0 inflateReset2
Error Message Summary:
FatalError:
Segmentation fault
is detected by the operating system.[TimeInfo: *** Aborted at 1715786295 (unix time) try "date -d @1715786295" if you are using GNU date ***]
[SignalInfo: *** SIGSEGV (@0x0) received by PID 207 (TID 0x71e2902e2b80) from PID 0 ***]
Segmentation fault (core dumped)
root@f76833e33ee6:/code/build/data# `
so the mysterious part is that when I was running a simple code for paddleocr, it was running hassle-free, but when I was testing and end-to-end operation (in whcih that snippet of paddleocr code was a part),
W0517 10:10:58.219796 252 default_variables.cpp:95] Fail to fscanf: Success [0]
this is the warning log I am getting. Anything concerning about this log?The text was updated successfully, but these errors were encountered: