Nikita Ivchenko

It might be useful for some one. I created the following interceptor to solve this issue: ```kotlin class WebSocketAuthenticationInterceptor( private val jwtDecoder: ReactiveJwtDecoder, ) : WebSocketGraphQlInterceptor { private companion object...

Привет, та-же проблема. Как вариант - можно кодировать символы юникодом, ну или просто их удалять, пока нет альтернативы. Да, кстати, это работает не только с мутом. Сегодня пытался забанить игрока...

After switching from TCP to UDP the problem has disappeared: the memory becomes stable. 

Hello. Most likely you are right and memory leaks could also appear when reading existing stream. Right now we are publishing 12 streams to mediamtx server and have ~100 readers....

Here is the dump created right after the launch: ```bash root@streaming-prod:~# go tool pprof -text http://localhost:9999/debug/pprof/goroutine Fetching profile over HTTP from http://localhost:9999/debug/pprof/goroutine Saved profile in /root/pprof/pprof.mediamtx.goroutine.002.pb.gz File: mediamtx Type: goroutine...

I don't think that we really had 150 active readers... However we have some readers, that often reconnects. Maybe mediamtx didn't close those connections for some reasons and still trying...

It looks like I have the same thing. On simulator everything works fine, but then I tried to install it on my device, using `react-native run-ios —device "iPhone Munoon"`. Here...

Yeah, this demo was launched on `^1.2.0-beta.1"` version. `"react-native-custom-fonts": "^1.2.0-beta.1"` setting in `package.json`. By the way, after I tried to launch it on my device, it was broken on simulator...

Sure, here it is: ``` 'Lacquer': { uri: "http://localhost:8080/resources/fonts/lacquer/lacquer-v1-latin-regular.ttf", fontFamily: "Lacquer", fontWeight: "400", fontStyle: "normal", color: "white" } ``` Yes, I'm sure, that server is running and font downloading properly....

Just discovered that you are right. If you close the error - font is loaded correctly!