Too many logs per second, v3.1

[papampi]

Updated to latest pre-release 3.1 and getting this error and then it completely stops the profile after 2 or 3 time :

[Error] Too many logs per second
[Error] Core exited, restarting.
>>>>>>>> Stopping profile [VLESS] xxxxxxxxxxxxxxxxx
[Error] gRPC: QNetworkReply::NetworkError code: -1919
V2Ray: 8134d3cc Neko: nekoray-3.1-2023-05-17
2023/05/17 07:06:14 nekoray_core grpc server listening at 127.0.0.1:11523
[Error] Core exits too frequently, stop automatic restart this profile.

[hingbong]

[Error] Too many logs per second[Error] Too many logs per second
[Error] Core 退出，正在重新启动。
>>>>>>>> 正在停止配置 [Shadowsocks] 香港 01
[Error] gRPC: QNetworkReply::NetworkError code: -1919
sing-box-extra: 1.3-b12-2 NekoBox: nekoray-3.1-2023-05-17
2023/05/17 10:25:04 nekobox_core grpc server listening at 127.0.0.1:51051
[Error] Core 退出太频繁，停止自动重启

i got it too

[arm64v8a]

Full log? It should only occurs if your core outputs more than 100 lines of log pre second.

[papampi]

I use my nekoray on an ubuntu desktop as my home default gateway with lots of devices connecting to it
Every now and then my nekoray log shows a long list of ips probably more than 100 scroll very fast.
I think it's not a good idea to stop or restart because of that.

[arm64v8a]

Please temporarily turn off logging or set loglevel to error.

This feature is to prevent abnormal resource usage due to loopback etc. If you don't stop core in this case, the whole system will lag as a result.

We need an appropriate limit value or roll back this feature.

[papampi]

I thought that should be the reason, but check this part of my log, this shows up very often.
Over 300 lines in just a second, and I should add my ubuntu workstation is very fast, same could cause real problem on slower machines
I think its best to add an option in the settings, so users can set it base on their needs and pc limits.

Nekoray.log

[papampi]

Please temporarily turn off logging or set loglevel to error.

On v2ray core I set my log level to none, with no effects. it kept logging and stopping, roled back to 2.28 for now.

[arm64v8a]

3.2版本回退了有关更改。因此core异常刷日志导致gui卡死的问题暂时无法解决。