-
Notifications
You must be signed in to change notification settings - Fork 7.2k
-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
deadlock after call esp_bluedroid_disable() (IDFGH-8175) #9672
Comments
Hi @fzboffice , If If it still doesn't solve your problem, please provide a demo that can reproduce the issue. Thanks |
@xiongweichao hello,I call esp_bluedroid_disable in my task.The same code behaves differently under different commit.This question only appear after pulling commit 134170a |
Hi @fzboffice , Please verify if this patch solves your problem. Thanks |
@xiongweichao Thank you , The problem has been fixed. |
…xt() after calling esp_bluedroid_disable() Closes #9672
…xt() after calling esp_bluedroid_disable() Closes #9672
…xt() after calling esp_bluedroid_disable() Closes #9672
…xt() after calling esp_bluedroid_disable() Closes #9672
…xt() after calling esp_bluedroid_disable() Closes #9672
Answers checklist.
IDF version.
v4.4.2-174-g134170a6fc
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
No response
Development Kit.
Custom Board
Power Supply used.
External 3.3V
What is the expected behavior?
调用esp_bluedroid_disable()后应正常
What is the actual behavior?
调用esp_bluedroid_disable()后被死锁
Steps to reproduce.
在idf commit 134170a 后出现
Debug Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: