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
The replicationCacheMaster() function expects the master pointer to be
non-nullptr and the cached_master to be nullptr. But if we happened to
get disconnected multiple times and thus also go multiple times through
replicationCreateMasterClient(), then we end up with both master and
cached_master being non-nullptr, which then triggers an assertion in
replicationCacheMaster() which crashes the server.
When we are recreating the master struct, mark cached_master for
asynchronous freeing, and reset its pointer.
Fixes: Snapchat#849
Crash report
Paste the complete crash log between the quotes below. Please include a few lines from the log preceding the crash report to provide some context.
Aditional information
The text was updated successfully, but these errors were encountered: