The patch I landed in bug 1011110 fixes the symptom, but the root cause remains. We are dispatching a BluetoothRequestParent::ReplyRunnable twice. That causes us to Send__delete__ on the underlying actor twice. I fixed the code to not call Send__delete__ again, but we should figure out where we are dispatching the runnable from and fix that. We should probably audit all of the places where we dispatch the runnable and ensure that we null out whatever pointer we have to it, which will prevent us from dispatching it a second time.
Thanks, Kyle. I will follow up this bug see if we can identify dispatch runnable twice.
Assignee: nobody → shuang
Target Milestone: --- → 2.0 S4 (20june)
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.