MeshCentral: Meshagent : uncaught "cannot push beyond allocated stack"

I used the router this morning to set up an HTTP connection to a remote host and after about 2 mins, I lost my connection and a message appeared in my terminal

uncaught: 'cannot push beyond allocated stack'

Normally when I see “stack” issues, I’d guess it to be a memory issue - would that be the case here? I’m running 32GB RAM on an Ubuntu 18 desktop host and have a fair few applications running at the same time (including VMware workstation which is quite memory hungry) but wanted to check in to see if there was anything that I can do from an MC2 point of view that can corroborate my assumptions?

About this issue

Original URL
State: open
Created 3 years ago
Comments: 16 (6 by maintainers)

Most upvoted comments

Bryan has a fix for this, has his been pushed into the MeshAgent GitHub and it’s going to required an update to the native C code, so the next version of the meshagent.exe. The bug will always happen after some number of handled routing connections. It will happen in both MeshCMD and the MeshAgent, so this is an important fix. Bryan has an agent candidate ready, but it needs to be tested very well before being released so this should be later this week or next week depending on how well the agent does in testing.

Ylianst on Jul 28, 2021

Sent instructions to Bryan to replicate this. Hopefully it’s an easy fix.

Ylianst on Jul 24, 2021

Ok, so it doesn’t appear to be an issue when I’m running an SSH route. However, when I’m running an HTTP, I do see it:

dave@dave-OptiPlex-5040:~/$ Redirecting local port 52080 to remote port 80.
Press ctrl-c to exit.

dave@dave-OptiPlex-5040:~/$ date
Thu Jul 22 10:05:37 PDT 2021
dave@dave-OptiPlex-5040:~/$ 
[2021-07-22 10:14:40 AM] uncaught: 'cannot push beyond allocated stack'
dave@dave-OptiPlex-5040:~/$

D4V3M0NK on Jul 22, 2021