Xray-core, a network tool enhancing the XTLS protocol for proxy management, is experiencing active development with a focus on improving networking capabilities and API functionalities. However, recent reports of memory leaks and connection stability issues, particularly with new features like SplitHTTP, pose significant challenges.
Recent issues and pull requests (PRs) highlight ongoing efforts to address memory management and connectivity problems. Notable issues include #3714 regarding memory leaks on Windows 11 and #3560 related to HTTP/3 multiplexing bugs. These issues indicate a need for improved resource management and compatibility testing.
The development team has been actively committing changes, focusing on feature enhancements and bug fixes. Key activities include:
This activity reflects a collaborative environment with a focus on maintaining code health and introducing new features.
Overall, while Xray-core continues to evolve with new features, addressing memory and stability issues will be crucial for sustaining its growth and user satisfaction.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 4 | 5 | 8 | 3 | 1 |
| 30 Days | 26 | 24 | 111 | 20 | 1 |
| 90 Days | 98 | 94 | 575 | 76 | 1 |
| 1 Year | 217 | 200 | 1199 | 180 | 1 |
| All Time | 2122 | 2100 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| mmmray |  |
1 | 11/14/0 | 14 | 98 | 2686 |
| yuhan6665 |  |
3 | 5/4/0 | 12 | 35 | 1985 |
| nobody |  |
1 | 2/2/0 | 2 | 8 | 487 |
| 风扇滑翔翼 |  |
2 | 6/3/4 | 5 | 8 | 312 |
| lelemka0 |  |
1 | 1/1/0 | 1 | 5 | 282 |
| RPRX |  |
1 | 0/0/0 | 7 | 8 | 89 |
| dependabot[bot] |  |
1 | 11/10/1 | 10 | 2 | 77 |
| mayampi01 |  |
1 | 0/1/0 | 1 | 2 | 68 |
| HunterQ |  |
1 | 4/2/2 | 2 | 3 | 63 |
| curlwget |  |
1 | 1/1/0 | 1 | 5 | 10 |
| Lumière Élevé |  |
1 | 1/1/0 | 1 | 1 | 4 |
| チセ |  |
1 | 2/1/1 | 1 | 1 | 3 |
| definitio |  |
1 | 1/1/0 | 1 | 1 | 2 |
| None (xiaorouji) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Andrevich (1andrevich) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Hossin Asaadi (hossinasaadi) | 0 | 1/0/0 | 0 | 0 | 0 | |
| 冬花ice (flowerinsnowdh) | 0 | 1/0/1 | 0 | 0 | 0 | |
| ahmadreza (radioactiveAHM) | 0 | 2/0/2 | 0 | 0 | 0 | |
| None (dragonbreath2000) | 0 | 1/0/0 | 0 | 0 | 0 | |
| None (ll11l1lIllIl1lll) | 0 | 1/0/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The XTLS/Xray-core project currently has 22 open issues, with recent activity indicating ongoing discussions and troubleshooting efforts among users. Notably, several issues highlight concerns regarding memory leaks, connectivity problems, and protocol compatibility, particularly with the new SplitHTTP feature and its interactions with various transport protocols. A recurring theme is the difficulty in maintaining stable connections under specific configurations, especially when using the Reality protocol.
Several issues exhibit significant user engagement, with participants sharing detailed logs and configuration files to diagnose problems. There is also a clear interest in enhancing features such as routing capabilities and improving compatibility with existing web services.
Issue #3721: VLESS-XTLS-uTLS-REALITY the Edge browser will display a 403 error message
Issue #3714: Memory leaks on the Xray-client on Windows 11 using Xray 1.8.17
Issue #3699: panic with this error
Issue #3683: vless入站+wireguard出站不通
Issue #3669: ERROR - X-UI: Failure in running xray-core: exit status 0xffffffff
Issue #3221: Memory leak
Issue #3560: SplitHTTP h3 h2 multiplex controller
Issue #3403: [Feature Request] https h2 proxy
The current state of open issues in the XTLS/Xray-core project reflects both active community engagement and ongoing challenges related to memory management and connectivity under specific configurations. The focus on enhancing routing capabilities and addressing performance issues indicates a responsive development environment that seeks to meet user needs effectively.
The analysis of the pull requests (PRs) for the XTLS/Xray-core repository reveals a total of 14 open PRs, with a significant focus on enhancing functionality related to DNS, UDP protocols, and various API improvements. The recent activity indicates ongoing development efforts aimed at improving performance and user experience.
PR #3728: Support DNS queryStrategy config for UDP NameServer
PR #3711: UDP noise
PR #3644: API: Add new Get Inbound User
PR #3637: API: Add user online stats
PR #3613: SplitHTTP client: Add multiplex controller for H3 & H2
PR #3730: Update go 1.23
PR #3729: Bump github.com/vishvananda/netlink from 1.2.1 to 1.3.0
PR #3719: Bump github.com/vishvananda/netlink from 1.2.1-beta to 1.2.1
PR #3718: Fix data leak between mux.cool connections
The current set of open pull requests reflects several key themes and areas of focus within the XTLS/Xray-core project:
A notable trend among the recent PRs is the emphasis on improving networking capabilities, particularly concerning DNS and UDP protocols. For instance, PR #3728 introduces a configuration strategy for DNS over UDP, which is essential in environments where traditional TCP-based DNS queries may be blocked or throttled. Similarly, PR #3711 proposes a method to obfuscate UDP traffic by introducing noise packets, showcasing an innovative approach to circumventing network restrictions imposed by ISPs.
Several PRs are dedicated to enhancing the API functionality of Xray-core. The introduction of new endpoints (e.g., PR #3644) and tracking capabilities (e.g., PR #3637) demonstrates a commitment to providing developers with robust tools for managing user sessions and monitoring network activity. These enhancements not only improve usability but also align with modern practices in software development by ensuring that APIs are both comprehensive and easy to use.
The draft nature of PR #3711 indicates an active engagement with the community, as contributors seek feedback before finalizing their implementations. This collaborative approach fosters an environment where ideas can be refined through discussion, ultimately leading to more robust solutions.
Despite the positive trends, there are some anomalies worth noting. For example, PR #3711 has been marked as a draft due to its experimental nature, which raises questions about its stability and potential impact on existing functionalities if merged prematurely. Additionally, there is a recurring theme of discussions around the implications of merging multiple experimental features simultaneously, as highlighted in discussions regarding fragmentation methods (e.g., PR #3677). This could lead to increased scrutiny from ISPs and potentially result in quicker blocking of these features.
While there has been significant activity in terms of open pull requests, there appears to be a lack of recent merge activity on older PRs. This could indicate bottlenecks in the review process or prioritization challenges among maintainers. Addressing this issue may require streamlining review processes or increasing contributor engagement to ensure timely integration of valuable contributions.
In summary, the XTLS/Xray-core repository is experiencing active development focused on enhancing networking capabilities and improving API functionalities while navigating challenges related to community engagement and feature integration. The balance between innovation and stability will be crucial as the project continues to evolve.
RPRX
yuhan6665
Summary
Quantified Reports
Detailed Reportsapi and go123.dependabot[bot]
github.com/vishvananda/netlink and github.com/cloudflare/circl.mmmray
Fangliding (风扇滑翔翼)
curlwget
chise0713 (チセ)
jadeydi (HunterQ)
PoneyClairDeLune (Lumière Élevé)
vrnobody (nobody)
definitio
mayampi01
lelemka0