CubeSA - Sus RAM behaviour

Hello Dear MikroTik forum

I am here with really strange behaviour on one of our CubeSA 60GHz APs. Device is running for about half year with only ONE client connected and we noticed it started to reboot itself. From observation, device just runs out of RAM and then restarts. But i noticed it only happens when there is no client connected (i suppose client started to turn off his the device to save electricity or something, does not matter).

Once the client disconnects, the device runs normally for about a hour and then RAM starts filling up until it crashes. I have two screenshots of memory usage here.

In the first image you can see the device run normally, until 10 PM, then client disconnects and problem occurs, fill up RAM → Crashes → Reboot → Repeat

The blank usage from 6 AM was caused device not booting again, i rebooted it remotely via POE Switch.
Then the device repeats it cycle until client connects again at about 1 PM, then the RAM stops filling but keeps the usage high until i rebooted it at 6 AM next day.

I post my config here, i replaced all sensitive info with ‘notforyou‘

/interface bridge
add admin-mac=04:CE:14:F6:F8:3A auto-mac=no name=bridge1 port-cost-mode=short
protocol-mode=none
/interface w60g
set \[ find \] disabled=no frequency=66000 name=wlan60-1 password=
"notforyou"
put-stations-in-bridge=bridge1 region=no-region-set ssid=notforyou
/interface w60g station
add mac-address=04:CE:14:F6:F8:3A name=wlan60-station-1 parent=wlan60-1
remote-address=F4:1E:57:E5:31:16
/interface wireless security-profiles
set \[ find default=yes \] supplicant-identity=MikroTik
add authentication-types=wpa-psk,wpa2-psk eap-methods=""
management-protection=allowed mode=static-keys-required name=notforyou1
static-algo-0=40bit-wep static-key-0=notforyou supplicant-identity=""
add authentication-types=wpa2-psk eap-methods="" management-protection=
allowed mode=dynamic-keys name=notforyou2 supplicant-identity=""
wpa2-pre-shared-key=
"notforyou"
/interface wireless
set \[ find default-name=wlan1 \] band=5ghz-onlyac country=no_country_set
default-authentication=no disabled=no frame-lifetime=10 frequency=5540
frequency-mode=superchannel hw-protection-mode=rts-cts
hw-protection-threshold=256 hw-retries=5 mode=ap-bridge radio-name=
notforyou
security-profile=ISFO_WPA ssid=notforyou wireless-protocol=802.11
wps-mode=disabled
/ip pool
add name=dhcp_pool0 ranges=172.17.220.10-172.17.220.100
/ip dhcp-server
add address-pool=dhcp_pool0 interface=bridge1 lease-time=20h name=dhcp1
/snmp community
set \[ find default=yes \] addresses=notforyou/32 read-access=no
add addresses=notforyou/32 name=notforyou
/user group
set read policy="local,telnet,ssh,read,test,winbox,web,sniff,api,romon,rest-ap
i,!ftp,!reboot,!write,!policy,!password,!sensitive"
/interface bridge port
add bridge=bridge1 interface=wlan1
/ipv6 settings
set disable-ipv6=yes
/ip address
add address=172.17.220.1/24 interface=bridge1 network=172.17.220.0
/ip dhcp-client
add interface=ether1
/ip dhcp-server lease
add address=172.17.220.10 client-id=1:f4:1e:57:e5:31:16 comment=
notforyou mac-address=F4:1E:57:E5:31:16 server=dhcp1
/ip dhcp-server network
add address=172.17.220.0/24 dns-server=notforyou gateway=172.17.220.1
ntp-server=notforyou
/ip dns
set servers=172.16.1.1
/ip service
set telnet disabled=yes
set ftp disabled=yes
set www port=88
set api disabled=yes
set api-ssl disabled=yes
/radius
add address=notforyou require-message-auth=no secret=notforyou
service=login
/snmp
set enabled=yes trap-community=notforyou trap-generators=""
trap-version=2
/system clock
set time-zone-name=Europe/Prague
/system gps
set enabled=yes port=gps
/system identity
set name=notforyou
/system note
set show-at-login=nos
/system ntp client
set enabled=yes
/system ntp client servers
add address=notforyou
/user aaa
set exclude-groups=full use-radius=yes

Sw Version is 7.18.2, also this is a second device, we replaced first one with this, because we tought that the device is faulty, but now the second device behaves the same.

If anyone encountered this, or have an idea, what might cause this or how to trace it, i will be happy for any feedback. Thank you.

Do you have any idea when those reboots started to happen ?
After upgrade to 7.18.2 maybe ?

Normally when the device reboots because of out of memory condition, there should be an autosupout.rif file.
You can create a ticket to support including this file so they can investigate what's wrong.
Personally I would also move to 7.19.6 (7.20.x I wouldn't recommend now, too many problem reports there for my liking)

Thank you for your answer.

Unfortunately, I don’t know when the first device started behaving this way. When we replaced it with the second device, I immediately installed version 7.18.2 on it and it was running fine until recently.

I will try to create ticket with supout, also i will try version 7.19.6 to see any if it changes, client is now connected, i have to wait until he disconnects again.