-
-
Notifications
You must be signed in to change notification settings - Fork 172
Add optional clearing of scan results when stopping scan. #304
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
Conversation
This resolves a possible collision when scanning is active and a call to connect to a device is made. When the scanner is still active in a continuous scan the results may be pushed at the same time as clearing them in the call to stop scanning when attempting to connect to a device. This propses to add a parameter to the scan stop call to not clear the scan results in this scenario and may be useful for other use cases.
|
The call stack in this looks odd. Can you provide more of the log? Also the register dump would help. |
I've been able to reproduce some similar errors to this. The problem results mainly from calling In your project I propose 2 possible solutions, put the scan task on core 0, or wrap the call in the loop to start the scan with In the meantime I will see what can be done to prevent this once I can trigger more crashes. |
OK, i've made the |
8 hours uptime so far! MUCH better. |
Yeah, You can close this we're good. |
This resolves a possible collision when scanning is active and a call to connect to a device is made.
When the scanner is still active in a continuous scan the results may be pushed at the same time as clearing them in the call to stop scanning when attempting to connect to a device. This propses to add a parameter to the scan stop call to not clear the scan results in this scenario and may be useful for other use cases.