Well, what's funny about that is he's allocated 1024 and MT is using only like 200. Javaw is using like 800+, however. Veg recommends stack size 10, but that has always struck me as way too high.
Also, just to clarify, these errors are cropping up when he isn't having the lag error mentioned earlier, but it does seem macro related.
Yea.... 10 really is way to high for a stack size. subdividing the macros up more will help that, but either Veggie has to do that or someone will have to take over. I used his older version, but since he pushed his stack size up to 10 suggested, I have looked around for alternatives( settled on Rumble's Slim but have/will make additional tweaks to it).
It is "possible" that something in one or more macros is calling putToken(the java method that transfers tokens from one machine to the server and then back out to clients) before the macro is finished. I THOUGHT we had all of those cleaned up, but it is always possible something was missed.
You say he is the GM? If so, and he has poor throughput on the upstream side, then his poor network is probably choking with sending all of those updates out the the clients when a token is changed(and the more clients, the worse it will be). Have someone(who has a good upstream speed) else host the server for a night and play with the same settings and see if it makes it any better. Best case scenario is that his network card or router are messed up(well, best case in terms of quick fixes if he has the money to replace that is) and the issue is not due to an ISP issue as they are generally pretty blah to work with in these types of cases. A second machine on his network might help rule out the network card(might also want to have him check the network FAQ as it's possible a few config changes to his network card settings "might" help. Likewise, removing his router and doing a direct connect might rule that out. Using something like DSLreports will give you a general baseline for upload and download speeds to see if changes make a difference or not.