Skip to content
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

Opus.lib: 1.3.1 version crashing in some windows machines in opus_encoder_create #342

Closed
Preethiravi196 opened this issue May 3, 2024 · 2 comments

Comments

@Preethiravi196
Copy link

Hi, I have an application that captures and streams audio over a websocket connection. Before sending over websocket, audio data is encoded using OPUS. This application works in most of the devices, where in some devices it crashes with the error in windows event viewer.

Using Windows Error Reporting, I was able to capture the dump and found that error occurs in the below segment of code with 0xC000001D: Illegal Instruction exception,

OpusEncoder* encoder = opus_encoder_create(Sample_rate , channel_count , app_type , &err);

I have compiled the lib in visual studio 2019 compiler with with no enhanced instruction set option and platform toolset: Visual Studio 2017.

Issue was observed in the devices with below proccessors,

  • intel xeon processor x5690
  • intel xeon processor x5560
  • intel64 family 6 model 158 stepping 10 genuineintel 2112 mhz
@Preethiravi196 Preethiravi196 changed the title Opus.lib: 1.3.1 version crashing in some windows machines Opus.lib: 1.3.1 version crashing in some windows machines in opus_encoder_create May 3, 2024
@xnorpx
Copy link
Contributor

xnorpx commented May 3, 2024

You don't give any information what buildsystem is used. But there was an avx2 bug in cmake for windows in early 1.3.1. So you could upgrade to a later Opus version or turn off intrinsics or patch the cmake scripts to remove the avx2 flags.

@Preethiravi196
Copy link
Author

Preethiravi196 commented May 14, 2024

Using 1.4 opus built in SSE2 instruction set configuration does not make the application crash. Thanks for your inputs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants