-
-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: potential deadlock in Subscriber #584
Conversation
Hello, Does it affect performance in any case (again select case uh oh)? Benchmark results are the same, right? I don't remember when it was added but I think subscribers were not closing correctly and memory was leaking or whatever... Thanks! |
I didn't check performance yet because currently... It just doesn't work. The tests are still failing. I think that this case has been forgotten in the new implementation, it was one of the reasons my previous implementation was so complex. I hope that we'll manage to find a solution without partially reverting #578. |
f313559
to
21cd1d2
Compare
The fix looks ok now. Here are the benchmarks: Before:
After:
@divine would you mind to test this patch in prod to see if doesn't introduce a regression? |
Hello @dunglas, Sure, I'll let you know the results in a few days. Thanks! |
Fixes https://github.com/dunglas/mercure/pull/578/files#r748726493.