Finn Bear

> Yeah there isn't really one besides using the false positives list. It would take some work on your end, but you could process [*my* comprehensive false positives list](https://github.com/finnbear/rustrict/blob/master/src/false_positives.txt) in...

> this could also be a good place to use go:embed (then decode on init() possibly) True! The downside here is that you would be including the entire list, when...

@gkjohnson yes this would solve my issue. My only comment is that, if layers are recursive, the current default layer mask is flawed. In my opinion, the default should be...

> I do not vote to make this change and leave the code as it is for greater flexibility. Currently, Layers can only be manipulated additively. In other words, you...

Just thought of one more thing. Three.js allows the user to specify `Object3D.DefaultMatrixAutoUpdate;`. In the same way, it could allow the user to specify `Layers.DefaultMask`. If this were the case,...

> Why do you mention actix's context wait queue ? The wait queue will indeed block the actor from doing pretty much any other processing, that's its intention, but where...

> A minimal reproduction example repo would be helpful for determining how to help. Sure, I put one on the `ws-mre` branch: https://github.com/finnbear/actix-tcp-leak/tree/ws-mre > What OS are you using? Server...

> Are you aware of any workarounds for it? See my original issue. A good enough workaround is to send pings periodically, and terminate the connection rapidly enough if pongs...

> Why you change `.lock()` to `.try_unlock` you will notice a bunch of errors where something is trying to access Mutex when it is blocked by another asynchronous function. I...

> @finnbear thank you for all your time. I was experiencing different issues, but your case still seems to be a bug. No problem, glad you were able to resolve...