Just had an alert from a managed server that memory was getting low. Winbox is using an awful lot of RAM even though it's only got 5 windows open. It has been left running for over a week.



Open windows:

Is this a request? Supouts should go to Mikrotik Support if you think there is a bug.

I'm not going to bother support until somebody else mentions it as right now it could equally be a problem with the host computer. The host needed updates so I've installed and rebooted. Will leave Winbox running for several days again. On start-up, it's using 43MB.

Is this a request? Supouts should go to Mikrotik Support if you think there is a bug.

Not possible. There is no Supout for Winbox.exe

Winbox would be v3.40 or whatever version of Winbox you are using. Maybe add connecting to a v7.14 router.

winbox64.exe consuming more RAM than java.exe. Congratulations MikroTik! That's an achievement

Winbox would be v3.40 or whatever version of Winbox you are using. Maybe add connecting to a v7.14 router.

Sorry my bad, was looking at the version of the box connected to. Yes, it's v3.40 and already up to 74MB after a couple of hours. I've saved the session - does that save the open windows? But for the record they're DHCP server, CAPsMAN, File List, Terminal and Wireless Tables. I'll leave it a few days and then close windows to see if that makes any difference.

winbox64.exe consuming more RAM than java.exe. Congratulations MikroTik! That's an achievement

LOL - the Java app is the UniFi controller also running on the same box.

Yes, it's v3.40 and already up to 74MB after a couple of hours.

I connect to my CCR1036 and it is using 30MB of RAM, if I open the address-list page it starts climbing... Gets to 100MB before it has finished loading..

Routes window.. Don't know.. I've never waited long enough for all of them to load. haha

24 hours later and WinBox is up from 43MB to 280MB working memory. At that rate, it would get to 1GB in about a week. So sounds like either a memory leak or a design problem whereby something grows without check.

Last time, send a report of any kind to MT, stating it here isnt going to fix it.

As I said, still waiting for somebody else to confirm the problem. Plus we discuss lots of bugs on here first before deciding it really is a bug. Not going to fire off a support email for every single problem I encounter esp. as they're often not a bug but a misunderstanding of something.

So sounds like either a memory leak or a design problem whereby something grows without check.

Which is still a memory leak..

I have no reason to doubt it.. I don't watch Winbox that closely and my systems have Winbox using a lot of RAM in the first place.. From memory, at least a few of the Winbox updates have been for memory leaks in the past.

I get the problem and it shouldn't happen but I'm stuck with something else.

Why would one keep Winbox open on a Windows computer for ... DAYS ??

I've got several sites where I've got an old laptop onsite for maintenance. Often leave it logged in running WinBox. That said, one has to question why I need to monitor the network so closely when I don't tend to do that with Unifi sites (ducks).

And what's wrong with VPN, an overlay network and then Winbox in from wherever you are ?

For my client I have 36 sites, all of them having at least 1 Tik device (mostly wifi-AP, some routers and switches). You really think I keep on each site a laptop OPEN for whenever it might be needed ??
36 laptops on top of the network gear ? I don't think so ...

I still don't understand why Winbox needs to be kept open... apart from the added security risk it poses.
For monitoring there are other tools. PRTG, NEMS, ZABBIX, ... maybe even ...(do I dare say it) The Dude.
Let those tools cover the alerting part. No need to waste time on watching things which mostly should be ok.
When there is an alert, then you need to look. Otherwise not.

Besides, it also consumes resources on the device itself because of the constant updating of whatever info you got on those screens.

Just my take on things

Very logical and well presented holvoe. Concur 100%.
Also I would recommend getting a CHR, one can get a cheap virtual router in the sky to connect all devices, via wireguard and thus all accessible right away.
SSTP as backup since MT to MT can be done easily without certificates

>And what's wrong with VPN, an overlay network and then Winbox in from wherever you are ?

Because at this site, the laptop also runs a legacy Unfi Controller so it was there already.

>I still don't understand why Winbox needs to be kept open... apart from the added security risk it poses.

It doesn't need to be kept open, I just don't bother closing it when the remote session locks on idle. It's inside the locked comms cabinet, locked inside a cupboard and screen locks on idle. Hardly a security risk.

>Let those tools cover the alerting part. No need to waste time on watching things which mostly should be ok.

To be fair, this particular site isn't too bad in terms of maintenance. But having recently upgraded to ROS 7, I'm just keeping a closer eye than usual.

All of the above is moot - this is just about a clear memory leak. Just so happens to be spotted at this site otherwise would probably never know. But if there is no interest in fixing bugs, well I'll look elsewhere.

But if there is no interest in fixing bugs, well I'll look elsewhere.

Nobody has said anything like that, other than you.

kevinds ( quite the opposite actually too ) Im reminded of some sayings....

"The price of inaction is far greater than the cost of making a mistake"

"In any moment of decision, the best thing you can do is the right thing, the next best thing is the wrong thing, and the worst thing you can do is nothing."

"Ignorance can be improved; willful ignorance and inaction is inexcusable."

"There are many roads to prosperity, but one must be taken. Inaction leads nowhere."

So ... create a support ticket.

Native WinBox for Linux is around the corner.

Re this - see my "rant" on viewtopic.php?p=1064802#p1064802 Not that I'm particularly asking for a Linux client. Only even tend to use Linux server with no desktop. But I personally think the interface effort should be more down the controller route - cloud hosted or running locally on a mid-level router.

Mikrotik Cloud Key - LOL. MT may not adopt other vendors management concepts blindly.

What does a silly rant about your inability to configure a capac have to with entering a support ticket for winbox ???

On topic: I can observe growing memory usage as well. Under Linux on Wine but it started off by about 80MB and now after a few hours it is 112M. So slightly growing. But as said: I suspect they are going to fix or hunt down such issues anymore. MT apparently has a "new" WinBox in development.

However: create a support ticket!

What does a silly rant about your inability to configure a capac have to with entering a support ticket for winbox ???

It was in reference to the comment about Linux client.

However: create a support ticket!

I will now that somebody else has confirmed it... that's all I was waiting for.

On topic: I can observe growing memory usage as well. Under Linux on Wine but it started off by about 80MB and now after a few hours it is 112M. So slightly growing. But as said: I suspect they are going to fix or hunt down such issues anymore. MT apparently has a "new" WinBox in development.

However: create a support ticket!

How do you know that I didnt tell infabo to write that up............... I mean he did go overboard, I said to write 30MB start and after a few hours to be 80MB.