The commit bacfdd58bbd5a18534601c84ce974d2ab2cc9a2f seems to have added an issue which causes g3proxy to use all CPU. Attached is a config that will reproduce. [broken_users.yaml.txt](https://github.com/user-attachments/files/16531660/broken_users.yaml.txt) Build command: ```cargo build -p g3proxy -p g3fcgen --features vendored-boringssl```