MikroTik

I've seen this now a couple of times, both with 7.14 and 7.14.1:
Basically reboot the cap AC, and watch its memory slowly but inexorably go down. Once it's above ~87% usage, the cap AC becomes unresponsive (time out waiting for process 85/24/etc), and I have to hard power cycle.

The interesting thing is that I have two of these, connected to same capsMAN, and only one does this for a while, then the problem moves to the other, etc.

Did anyone else see this? Is it a known issue? (Should I just move to cap AX with its 1GB of RAM?)

7.13.5, cap ac, wifi-qcom-ac, uptime 1week. free memory: 32.6mb

7.13.5, cap ac, wifi-qcom-ac, uptime 1week. free memory: 32.6mb

The actual free memory is less concerning than the fact that it continuously decreases between reboots. This is the same graph but over 6 months: you can clearly see that until 7.13 and the new wifi-qcom-ac drivers it was stable, since then it's not really stable - and seems to have gotten worse recently:
I don't know if it's capsman, the number of connected devices, or something else. But it doesn't seem stable at all.

What happened on 12/27?

What happened on 12/27?

That's when I upgraded to 7.13, but still using old drivers, if I remember correctly. My upgrade timeline:

- migrated host from hAP ac to cAP ac: 2023.11.22
- 7.12 → 7.13: 2023.12.24
- 7.13 → 7.13.4: 2024.02.08
- 7.13.4 → 7.14.1: 2024.03.24

So it was stable on 7.8 and 7.12, up until 7.13. Since 7.13, it's more or less leaking memory. Either 7.13 itself, or the wifi-qcom-ac drivers.

So basically you say, leaking memory since 7.13 and qcom drivers? What's odd, you already had only like 60mb free memory on 7.12 with capac.

Only 60MB free (out of 128MB) is not bad (for me). I'd be happy if I could stay there.

I've now disabled connection tracking entirely, and there was a reduction in memory usage, but the leak is still present. I'll probably file a support ticket, since it doesn't seem to be a widely known issue.

I can confirm this behavior, with one hap ac3 and wifi-qcom-ac drivers. Two other hap ac3, with legacy drivers don't show this behavior.

I can confirm this behavior, with one hap ac3 and wifi-qcom-ac drivers. Two other hap ac3, with legacy drivers don't show this behavior.

Oh, thanks, this is a good datapoint!