Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Noticed that possible memory leak occurred in xray-core with routing policies

Open
#104 11 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
go
Domain
networking

Research direction

Reproduce the gradual memory increase with Happ or V2BOX using xray-core 25.9 or 25.7 on iOS 18.7, while observing usage from the reported 12M baseline toward 50M. Narrow the issue to routing policies and identify a reproducible cause; done means memory no longer grows until the app crashes.

Written by the indexing model from the issue text.

Description

Both in Happ with xray-core 25.9 and V2BOX with xray-core 25.7 in iOS 18.7, I noticed that the memory used was gradually increasing from around 12M initially to finally 50M and made the app crash.

It took about from less than one hour to several hours for the final crash to occur.

If any further info about this topic is needed, I will provide as far as I can.

Dominant language
Go
Stars
229
Forks
170
Avg merge
42m
Merged PRs (30d)
10

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from XTLS/libXray

All issues in XTLS/libXray

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.