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
I have a test case now. If the same process joins a group, and also starts monitoring a group (or a scope), it works fine. But when such process gets terminated without leaving all groups (or stopping monitoring), pg assumes that a process is either a monitor, or a joined process.
Fix is technically trivial, upon getting {DOWN, ...} message check both monitors and locally joined processes. It may incur a small performance fee, @zzydxm would you be able to test it at scale?
Describe the bug
This will crash:
Expected behavior
pg should not crash
Affected versions
All version that includes the new pg
Additional context
Add one more case clause here should work: https://github.com/erlang/otp/blob/master/lib/kernel/src/pg.erl#L407
The text was updated successfully, but these errors were encountered: