`RangeError: Maximum call stack size exceeded` when voting on newly create posts
Sentry Issue: FRONT-4Q
RangeError: Maximum call stack size exceeded
at __tryOrUnsub (./node_modules/rxjs/_esm5/internal/Subscriber.js:200:17)
at next (./node_modules/rxjs/_esm5/internal/Subscriber.js:130:1)
at _next (./node_modules/rxjs/_esm5/internal/Subscriber.js:76:1)
at next (./node_modules/rxjs/_esm5/internal/Subscriber.js:53:1)
at notifyNext (./node_modules/rxjs/_esm5/internal/operators/mergeMap.js:84:1)
...
(45 additional frame(s) were not displayed)
added scoped labels
added 1 deleted label
removed 1 deleted label
added scoped label
added scoped label and automatically removed label
added scoped label and automatically removed label
assigned to @benhayward.ben
added 1 deleted label
added scoped label
added scoped label and automatically removed label
added scoped label and automatically removed label
added scoped label and automatically removed label
removed label
added scoped label
added 1 deleted label and removed 1 deleted label
removed label
removed 1 deleted label
added scoped label
changed weight to 4
changed time estimate to 4h
added scoped label and automatically removed label
changed milestone to %Sprint::01/15 - Youthful Yabby
changed due date to January 28, 2020
added scoped label
- Developer
Not able to trigger this voting on newly-created posts.
This mostly looks like it happens in groups so tested in them here:
- Group chat https://streamable.com/s/eo26f/yznwtg
- Group video https://streamable.com/jqexk
Edited by Ben Hayward added 30m of time spent at 2020-01-16
added scoped label and automatically removed label
- Developer
I also cannot reproduce this one. I am trying to sit in the H&S group because my intuition and the logs suggest this is leaky handlers, but I cannot reproduce it for the life of me.
@markeharding any ideas on how we might be able to fix / debug this one?