mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #3529] 0.51.0 panic: runtime error: slice bounds out of range [20:16] #2817
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#2817
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 @pierre-pretorius on GitHub (Jul 14, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3529
Bug Description
We did get the
slice bounds out of rangeerror in theciphercode in previous versions, but we upgraded to the latest 0.51.0 to ensure the bug is present in the latest code. It looks like the stack trace in the log below is too short to determine the root cause?frpc Version
Various versions from 0.34.0 and upwards
frps Version
0.51.0
System Architecture
linux/amd64
Configurations
Server
Client
Logs
Steps to reproduce
We only see this error on high traffic servers, so it's not easy to reproduce. It happens more or less every day.
Affected area
@fatedier commented on GitHub (Jul 17, 2023):
@pierre-pretorius I looked into it, but I couldn't figure out under what circumstances this issue would occur. It's quite strange. Are you using the binary files downloaded from GitHub or did you compile it yourself?
@fatedier commented on GitHub (Jul 17, 2023):
In addition, starting from version 0.50.0, TLS will be enabled by default. The traffic between frpc and frps will be encrypted, so you no longer need to use
use_encryption = true.@pierre-pretorius commented on GitHub (Jul 19, 2023):
I'm using the binary from Github
@fatedier commented on GitHub (Jul 20, 2023):
@pierre-pretorius I have discovered a race condition issue, but I am not sure if it is related to your problem. I will fix this issue and release a minor version.
@github-actions[bot] commented on GitHub (Apr 6, 2024):
Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.