Winbox Memory leak almost 1Tb used!

I thought Chrome was eating my Memory rarely am I ever into my 512gb Swap File

yesterday I pkill -9 ’d ’ all my Browsers so I could watch a video without it being choppy , then it happened again today so I investigated a bit further this time

Turned out to be winbox , Linux version on Ubuntu

looks like their is a new update so will see if my RAM’s all used up again next month up to ~ 28 days ago it was ran

looking at the routers up time 17 days since i rebooted them all so that’s how long winbox program was opened monitoring them

Can you please let us know which Windows do you keep opened in WinBox loader when you see this high memory usage/leak? Can you notice any pattern? For example, usage is fine, until you open “Interfaces“ menu, “IP/Route“ menu, etc.

pretty much had them opened on wifi

and might have had this opened as well

I was trying to do a mesh with WDS but every-time I tried the entire network worked only as good as the worst connection so gave up and went back to repeaters

currently only 1x winbox app running and its has 2gb allocated ~3hrs

and looking at the screenshot that winbox app was actually only running a bit over 2 days

and in the last 10 mins its used another 500mb so will see what its like in the morning

in the morning no change

if I notice it hogging RAM again what should I run / do ?

well it has not happened again since updating to what ever version was available Nov 14th

(no idea where to find version numbers of the currently running applications )

Just upgraded to v4.0beta42 and about to reload them all again

It could depend on the way you start WinBox, i.e. where the output is directed.

I now start WinBox with output to temp file, and I regularly observe this in the output:

Warning: qrc:/qt/qml/WinBoxQml/qml/WTable.qml:1777:25: Unable to assign [undefined] to QString (qrc:/qt/qml/WinBoxQml/qml/WTable.qml:1777, )

This is repeated over and over again. One of my tmp files is now 1.5G in size.

When this somehow ends up in memory it could explain your problem. In my case the memory footprint seems stable.

(before I made the special script to redirect output, I started WinBox directly from a desktop shortcut, and it turns out that the output is then redirected to syslog/journal and fills that with crud)