mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #3263] FRP遇到大量请求时客户方崩溃 #2615
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#2615
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KleeLoveLife on GitHub (Jan 19, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3263
Bug Description
使用FRP转发Minecraft时遇到压测时FRPC崩溃
frpc Version
0.46.1
frps Version
0.46.1
System Architecture
linux/amd64 -> windows/amd64
Configurations
[common]
server_addr = 114514
server_port = 7000
token = 114514
[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 25565
remote_port = 60009
proxy_protocol_version = v2
console or real logFile path like ./frpc.log
log_file = ./frpc.log
trace, debug, info, warn, error
log_level = info
log_max_days = 3
Logs
Steps to reproduce
...
nohup.tgz.log
Affected area
@fatedier commented on GitHub (Jan 20, 2023):
错误信息需要更完整的日志
@KleeLoveLife commented on GitHub (Jan 20, 2023):
client.log
@KleeLoveLife commented on GitHub (Jan 20, 2023):
client_end.txt
@KleeLoveLife commented on GitHub (Jan 20, 2023):
服务端见上nohup.tgz.log 删掉.log后缀
@xqzr commented on GitHub (Jan 20, 2023):
386?
如果 Windows 是 x64,可以尝试 amd64 版本
@fatedier commented on GitHub (Jan 29, 2023):
@KleeLoveLife 你后面补充的 client 端的日志还是没有完整的日志,看不到 panic 的原因。
但是从日志中协程数量来看的话,猜测大概率是协程很多,某个资源耗尽后异常退出了。
至于为什么会有大量连接,取决于你的测试过程了,除非有可以便于我本地复现的方法,否则也没法给到更多的帮助。
@github-actions[bot] commented on GitHub (Mar 1, 2023):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.