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

[Bug]: how to ensure the functon "wakeLwsServiceEventLoop " thread safety,because of "lws_callback_on_writable" is not thread-safe #1997

Open
1 of 3 tasks
fys85 opened this issue May 24, 2024 · 0 comments
Labels
bug Something isn't working needs-triage v1.7.3

Comments

@fys85
Copy link

fys85 commented May 24, 2024

Please confirm you have already done the following

  • I have searched the repository for related/existing bug reports
  • I have all the details the issue requires

Please answer the following prompt

  • This issue is replicable using the unmodified sample application

Describe the bug

as https://github.com/warmcat/libwebsockets/issues/2358 said ,lws_callback_on_writable is not thread-safe, so how to we ensure wakeLwsServiceEventLoop thread-safe

Expected Behavior

wakeLwsServiceEventLoop is thread-safe

Current Behavior

wakeLwsServiceEventLoop is not thread-safe

Reproduction Steps

wakeLwsServiceEventLoop is call in multi thread

WebRTC C SDK version being used

1.7.3

If it was working in a previous version, which one?

No response

Compiler and Version used

--

Operating System and version

--

Platform being used

arm

@fys85 fys85 added bug Something isn't working needs-triage labels May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage v1.7.3
Projects
None yet
Development

No branches or pull requests

2 participants