Skip to content

After upgrading to 3.15 the remaining quota is not visible at all - cc-switch

Quick fix

Upgrade cc-switch to 3.16.0 to fix usage not displaying. For high disk/CPU/GPU use, turn the local proxy or the routing master switch off.

Error output
3.13版本还是能够看到剩余额度的,升级了3.15版本就完全看不到剩余额度了
English translation

On version 3.13 I could still see the remaining quota; after upgrading to 3.15 it is not visible at all

In 3.15, a defect in the cc-switch usage statistics UI stopped the status bar and main screen rendering the remaining quota correctly. Fixed in 3.16.0.

Worth noting: this issue cluster actually mixes several independent problems from the cc-switch usage statistics and background sync modules. Besides usage not displaying, the underlying mechanism also produces these variants: 1) the local proxy writing to SQLite at high frequency (DELETE journal + FULL sync) driving disk IO to 100% (#5823); 2) tokio timers catching up after Windows wakes from sleep, spiking one CPU core (#5164); 3) the routing panel refreshing live, driving WebView2 GPU use high (#5760); 4) OpenCode session log duration hard-coded to 0 (#6326). Those resource problems are architectural design defects and can currently only be mitigated by turning the relevant features off.

  1. Upgrade cc-switch to 3.16.0 or newer to fix usage statistics not displaying in the status bar and main screen.

  2. If disk, CPU, or GPU use is abnormally high, go to 设置 → 路由 → 本地路由 (Settings > Routing > Local routing) and turn the routing master switch off, or turn the local proxy off outright, to stop the high-frequency background sync and WebView2 rendering.

Toolcc-switch
VersionUnknown
PlatformsWindowsmacOS
Why does GPU use stay high with routing on?
The routing panel and usage statistics screen refresh live, continuously re-rendering WebView2. Turning the routing master switch off in settings restores normal use.
Why does a mechanical hard drive (HDD) sit at 100% disk usage after startup?
The local proxy SQLite uses DELETE journal and FULL sync mode, and high-frequency small transactions produce hundreds of times write amplification. The stopgap is turning the local proxy off.
CPU stays pinned after Windows wakes from sleep. What now?
The tokio timer catches up on missed ticks when Windows wakes. Wait for the background session sync mechanism to be optimised officially, or quit cc-switch for now.

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.