You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a report error occurs and the queued report handler is executed after the SubscriptionCallback object is deleted, calling the report handler on the queue would cause a segmentation fault, like the following:
I didn't try myself but, in SubscriptionCallback::ReportData(), capture the callback blocks in the closure instead of capturing "this" object when queuing the handler callback:
Problem
When a report error occurs and the queued report handler is executed after the SubscriptionCallback object is deleted, calling the report handler on the queue would cause a segmentation fault, like the following:
Log leading to the fault:
Proposed Solution
I didn't try myself but, in SubscriptionCallback::ReportData(), capture the callback blocks in the closure instead of capturing "this" object when queuing the handler callback:
That is,
instead of
The text was updated successfully, but these errors were encountered: