Robert Mujica

Yes that is what it seems to be happening these threads are waiting in Monitor.Wait to re-acquire a lock which they released. And it seems a Monitor.Pulse or Monitor.PulseAll is...

Thanks for Quick response on this issue, will have new dump files tomorrow to do further analysis so i will share more details. But so far I share same thoughts...

That is the exact issue we are having. We dont see it normal. We are doing more test / analysis today with without this nuget. On Thu 21 Mar 2019,...

one more detail regarding our implementation that we believe maybe causing this issue of leaving many threads in waiting state, is that we are subscribing to 8 Channels ( one...

Basically - Overtime response time increases. e.g. our website should return within 2 seconds, but it starts taking 5, 9 and more seconds to respond. - And eventually it stops...

analyzing some of the recent logs ( from 22nd of March ) I can see following entries: Type: System.InvalidOperationException Message: Reading is not allowed after reader was completed. Stack: [HelperMethodFrame]...

@mscrivo no we kept 2.0.571, after further analysis i found in dump file Stackoverflow and OutofMemoryException that we believe is actual root cause of the issue we have. After i...

One more thing we did try was to minimize the number of Channels we use for Pub / sub, but after some analysis we found no differences between listening for...

Hey, having same issue, but i'm not using docker-swram, i'm using FastApi on k8s i made some changes to add following settings: max_inactive_connection_lifetime=900, min_size=5, max_size=10), but still seeing this issue,...