-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Update misplaced removal of an event handler. #13351
Conversation
PR #13351: Size comparison from fb154cf to 71d8e42 Full report (31 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Fast-tracking test change. |
I think existing code tries to avoid handler leaks or duplicate calls. Is 'remove' the right thing to do? How about scheduling a lambda to be executed on the chip thread at a later time? is that an option? I am not yet clear on what crashes here and why - it seems somewhat reasonable for the code to say "when executing current handler say that the current handler is obsolete". |
/rebase |
71d8e42
to
38ee631
Compare
PR #13351: Size comparison from 0e5bc69 to 38ee631 Full report (14 builds for efr32, k32w, linux, p6, qpg, telink)
|
38ee631
to
50f46a4
Compare
PR #13351: Size comparison from 36a759d to 50f46a4 Full report (19 builds for efr32, k32w, linux, mbed, p6, qpg, telink)
|
Problem
In simulated devices immediately after pairing, the simulated device crashes. This is due to the even being removed during the call of the event.
Change overview
Deleted line the removes the even handler.
Testing
Reproduced crasher and commissioned the simulated device successfully after change.