You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NOTE: The iperf3 issue tracker is for registering bugs, enhancement
requests, or submissions of code. It is not a means for asking
questions about building or using iperf3. Those are best directed
towards the Discussions section for this project at https://github.com/esnet/iperf/discussions
or to the iperf3 mailing list at iperf-dev@googlegroups.com.
A list of frequently-asked questions
regarding iperf3 can be found at http://software.es.net/iperf/faq.html.
Context
Version of iperf3: 3.16
Hardware:
Operating system (and distribution, if any): centos
Please note: iperf3 is supported on Linux, FreeBSD, and macOS.
Support may be provided on a best-effort basis to other UNIX-like
platforms. We cannot provide support for building and/or running
iperf3 on Windows, iOS, or Android.
Other relevant information (for example, non-default compilers,
libraries, cross-compiling, etc.): glibc-2.38-29
Please fill out one of the "Bug Report" or "Enhancement Request"
sections, as appropriate. Note that submissions of bug fixes, new
features, etc. should be done as a pull request at https://github.com/esnet/iperf/pulls
Bug Report
Long duration streaming with multiple threads resulted in segment fault on the client side at the end of the test.
Use the following command for testing:
server side: iperf -s
client side: iperf -c serverIP -t 2400 -P 8
At the end of the test, client side encountered segment fault.
Expected Behavior
Test completed normally.
Actual Behavior
The testing environment spans multiple network nodes.
iperf's management connection does not send packets for a long time, triggering a timeout for connectioin tracking on intermediate node.
At the end of the test, the client reclaimed the thread and sent an end message using the management connection, but the message was discarded by the intermediate link.
Resulting in management connection timeout, triggering thread recycling again.
When the number of threads reaches 5 or more, glibc has already unmapped the address pointed to by “sp->thr”, resulting in a segment fault during the second thread recycling.
Steps to Reproduce
Use the following command for testing:
server side: iperf -s
client side: iperf -c serverIP -t 2400 -P 8
Possible Solution
Enhancement Request
Current behavior
Desired behavior
Implementation notes
The text was updated successfully, but these errors were encountered:
bmah888
changed the title
sigfault when multi thread repeated recycling in client
segfault when multi thread repeated recycling in client
Sep 9, 2024
NOTE: The iperf3 issue tracker is for registering bugs, enhancement
requests, or submissions of code. It is not a means for asking
questions about building or using iperf3. Those are best directed
towards the Discussions section for this project at
https://github.com/esnet/iperf/discussions
or to the iperf3 mailing list at iperf-dev@googlegroups.com.
A list of frequently-asked questions
regarding iperf3 can be found at http://software.es.net/iperf/faq.html.
Context
Version of iperf3: 3.16
Hardware:
Operating system (and distribution, if any): centos
Please note: iperf3 is supported on Linux, FreeBSD, and macOS.
Support may be provided on a best-effort basis to other UNIX-like
platforms. We cannot provide support for building and/or running
iperf3 on Windows, iOS, or Android.
libraries, cross-compiling, etc.): glibc-2.38-29
Please fill out one of the "Bug Report" or "Enhancement Request"
sections, as appropriate. Note that submissions of bug fixes, new
features, etc. should be done as a pull request at
https://github.com/esnet/iperf/pulls
Bug Report
Long duration streaming with multiple threads resulted in segment fault on the client side at the end of the test.
Use the following command for testing:
server side: iperf -s
client side: iperf -c serverIP -t 2400 -P 8
At the end of the test, client side encountered segment fault.
Expected Behavior
Test completed normally.
Actual Behavior
Steps to Reproduce
Use the following command for testing:
server side: iperf -s
client side: iperf -c serverIP -t 2400 -P 8
Possible Solution
Enhancement Request
Current behavior
Desired behavior
Implementation notes
The text was updated successfully, but these errors were encountered: