Increased ram consumption after update from 1.13.20 to 1.14.x

Operating system

Android

System version

17

Installation type

sing-box for Android Graphical Client

If you are using a graphical client, please provide the version of the client.

1.14.1

Version

Description

I was using sing-box 1.13.20 from github on pixel 8, android 17 (CP2A.260805.005), after updating to 1.14.0 i noticed significant increase of ram usage with the same config, 1.13.20 used 70-80mb of ram, now average ram consumtion is ~300mb, but sometimes im getting spikes to 500mb, presumably when watching videos.
for info and reproduction i have uploaded exported memory report from client, it is encrypted with age, but i had to strip of the .age from filename for github upload

censored client conf

{
  "log": {
    "level": "info",
    "timestamp": true
  },
  "dns": {
    "servers": [
      {
        "tag": "local-dns",
        "type": "https",
        "server": "9.9.9.9"
      }
    ]
  },
  "inbounds": [
    {
      "type": "tun",
      "tag": "tun-in",
      "address": "172.16.0.1/30",
      "auto_route": true,
      "strict_route": true
    }
  ],
  "outbounds": [
    {
      "type": "vless",
      "tag": "vless-out",
      "server": "xxx.xxx.xxx.xxx",
      "server_port": 8843,
      "uuid": "uuid",
      "flow": "xtls-rprx-vision",
      "tls": {
        "enabled": true,
        "server_name": "server_name",
        "utls": {
          "enabled": true
        },
        "reality": {
          "enabled": true,
          "public_key": "public_key",
          "short_id": "short_id"
        }
      }
    },
    {
      "type": "direct",
      "tag": "direct"
    }
  ],
  "route": {
    "rule_set": [
      {
        "type": "remote",
        "tag": "geoip-ru",
        "format": "binary",
        "url": "https://raw.githubusercontent.com/SagerNet/sing-geoip/rule-set/geoip-ru.srs",
        "download_detour": "direct"
      }
    ],
    "rules": [
      {
        "action": "sniff"
      },
      {
        "action": "resolve",
        "strategy": "prefer_ipv4"
      },
      {
        "protocol": "dns",
        "action": "hijack-dns"
      },
      {
        "ip_cidr": [
          "9.9.9.9/32"
        ],
        "outbound": "direct"
      },
      {
        "rule_set": "geoip-ru",
        "outbound": "direct"
      }
    ],
    "final": "vless-out",
    "auto_detect_interface": true
  },
  "experimental": {
    "cache_file": {
      "enabled": true
    }
  }
}

Reproduction

2026-09-03T05-51-13.zip

can be reproduced every time by using conf from appended archive

Logs

Supporter

• I am a sponsor

Integrity requirements

• I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
• I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
• I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
• I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.

Start by reproducing the report with the appended 2026-09-03T05-51-13.zip configuration on the Android client, comparing 1.13.20 with 1.14.x. Inspect the uploaded encrypted memory report and measure usage during normal operation and video playback. Done means identifying the regression's source and confirming that memory usage returns toward the earlier baseline.