Closed Raj2032 closed 3 months ago
After adding some extra code to pause before executing the next line until I press a key, it turns out it crashes when I end up right at this line:
The detect_words
call is the first function that actually does some machine learning inference. You can verify if this is the problem by using RTen's CLI tool to run the model directly with random inputs:
cargo install rten-cli
rten text-detection.rten
Does the machine that is crashing have any customization to the CPU settings in the BIOS, for example overclocking? Ocrs uses AVX instructions which apparently slightly increases the voltage if used. Tesseract also uses AVX instructions I believe, so it's interesting if that program does work.
As far as resolving the issue goes, there is not a whole lot I can do about hardware faults from my side, other than perhaps providing a way to disable usage of the more advanced instructions. The program will run more slowly (by ~2.5x or so) in that case.
@robertknight I am using stock bios settings, no overclockong or anything.
AVX instructions which apparently slightly increases the voltage if used.
Maybe I should just overvolt (not overclock) my CPU then, as there is not enough voltage going to the CPU then and the current stock bios settings is limiting it?
I also found this:
I may need to offset AVX.
Based on discussions elsewhere it seems like a hardware issue that is out of scope for this project to resolve. Per my last comment, I might add a way to disable the use of SIMD entirely in future (eg. via setting an environment variable or something).
it might be to do with a powersupply issue but yeah, anyways thanks! On Monday, 3 June 2024 at 16:31, Robert Knight @.***> wrote:
Based on discussions elsewhere it seems like a hardware issue that is out of scope for this project to resolve. Per my last comment, I might add a way to disable the use of SIMD entirely in future (eg. via setting an environment variable or something).
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
This is my code
using the command
cargo r
runs fine but runs too slowly. I was suggestd to use--release
flag as it runs much faster,So after running
cargo r --release
my computer crashes the second it runs. The computer will switch itself off so this is at a hardware level rather than at OS level. I tested this on both Windows and Linux same issue.After adding some extra code to pause before executing the next line until I press a key, it turns out it crashes when I end up right at this line:
I am not too sure how to resolve this at all, especially when my PC shuts itself off immediately as soon as it reaches this line. Not too sure if this is doing GPU task or CPU task?
CPU is:
Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
as mentioned in the title, this happens on my gaming desktop computer (10 years old) but not on my non gaming more modern laptop with a weaker CPU.
Does this have to do with some unstable version of
cargo
or some unstability on some CPUs out there?