Re: Finalizers are dangerous
See comments inline …
No, we shut down the bridges to prevent events from firing. In some cases (and certainly *not* all) that also releases resources acquired when the bridges were opened, which is a Good Thing.
It’s not up to you. As I said before, it’s my application, and I get to decide what leaks are worth worrying about. One-time leaks that don’t grow over time don’t concern me, and the cost of eliminating them is not worth it in almost all cases. (Again, that’s my choice — “Perfect is the enemy of good enough”).
As you are well aware, that is not a solution — it doesn’t stop events from firing, which is the real reason for shutting down the transport.
What configuration option is that? How would it work?
I would be happy to submit a PR, but it doesn’t sound like it would be accepted. If we can agree on an approach I’ll see what I can come up with.
In the meantime I gave up and forked the code. As project maintainer I don’t imagine that’s what you want, but you’re not giving me a choice.