-
Notifications
You must be signed in to change notification settings - Fork 77
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
Illegal Instruction when AVX is not available on the Host #110
Comments
Hello @piotr-k-k , Are you using some specific wav file that you can share in order to reproduce the issue? Also, can you, please, try some examples from the "Examples" folder? |
Hello @sandrohanea, thank you for reply, no I didn't change anything and I used default kennedy.wav. I tested example Simple as well as my own test application, all with the same result. |
I still couldn't manage to reproduce the error. Can you, please, clarify the OS version and architecture(e.g. x64, arm64, x86) that you're using? |
I used Windows 10 x64, today later or tomorrow maybe I will try other system and hardware. |
that is one of the systems that I'm using, and can confirm that it should work (just tested it). |
Another possible issue might be similar with: https://stackoverflow.com/questions/59584105/illegal-instruction-from-vs-c-on-windows Which CPU are you using? |
Now I don't know what exactly CPU I use, I think it's some Intel Xeon, will check tomorrow. Thanks for tips, tomorrow I will continue deal with it. |
I dealt with this problem by rebuilding whisper.cpp with disabled AVX2, so with set WHISPER_NO_AVX2 variable. |
Thanks for confirming @piotr-k-k , |
Hi, unfortunatelly I get unhandled exception trying run Whisper.net.Demo and I can't deal with it.
Unhandled exception at 0x00007FFB6C6B3441 (whisper.dll) in Whisper.net.Demo.exe: 0xC000001D: Illegal Instruction.
at line
NativeMethods.whisper_full_with_state(currentWhisperContext, state, whisperParams, (IntPtr)pData, samples.Length);
VS2022, .NET 7, Whisper 1.4.7
Any suggestions?
Thanks
The text was updated successfully, but these errors were encountered: