High CPU usage

Satisfied with the experiment.
I based on kaz 5.3.5. Modified _sleep function done by GKevinOD, remove reduce memory function.

Result low or almost idling on bot CPU usage (result of modified _sleep), CPU @ idle around 50% and when bot working... Goes up to 60-70% then drop back around 50%.

As I played with bot restarter, didn't hang for last 12 hr...

As for GKevinOD 4.5.1, why it hang even with bot restarter and while training and idling... Could be due to frequent calling of dll using _regioncapture and doing pixel search during training... That's like 20 min of calling before army full... Probably that could cause the memory leak. In last few experience, many didn't experience the hang when barrack is boosted coz the training cycle is shorter...

So let's see how to reduce the stress in this area...

I dont even know which one is which seriously haha.. theres multiple coders making their own versions, why not stick together and go towards development of the same version instead of some others going back to 5.3 and releasing 5.3.1, when there is alredy 5.4 out for example.. just a tought, u guys do awesome work! Im following every day multiple times.

@Scorpio

Many people are trying to contribute for the devt of the bot but have varying level of expertise. So once a new version came out some try to stabilize it first while others work on other features. For example the previous release of v5.3.0, many bugs were present but then was stabilized at 5.3.1.. after then, a lot of features came out: 5.3.2 to 5.3.5. It's actually easier to debug part by part instead of one go. So expect the same for v5.4..

@dinobot

I've tried both restarter and stopstart. Eventhough stopstart releases all the loops in v5.3.1, it still hangs unlike the restarter. So I'm guessing if it has something to do with Dllopen without being closed (Dllclose). In the current version 5.4.1, a lot of new codes require more dll than the previous versions. I tried to research but I cannot find articles regarding problems arising from not closing opened DLL.