Leaderboard

Hey guys, I'm happy to let you know that the issue has been solved by the help from @LoWrIdErTJ - BotGuru ! He checked the code and recommended removal of the browser's "crash checkers", precisely "auto close browser crash" from Advanced Ubot plugin. Please pay attention to it if you use it. It might eat up half or more of your CPU power. For some reason, the Ubot Studio was ignoring this plugin when running opposite to when it was running as a compiled bot. So, the bot is now running like a charm with 1-2% of CPU usage most of the time! Thanks you all for the

You can try on another machine and compare the results. To find the problem is your system or uBot.

Does your UI have lots of input forms? In my experience that's the one causing it. Try to load your compiled bot without UI. Hardcode the variables needed to test it.

Best solution is to rollback to more stable version. I think some plugins are causing that because when you disable plugins commands are showing.

First off all, thanks to UbotStudio developers for creating this amazing tool. It helped my family from surviving from very bad financial situation. Im very thankful to Ubot developer team. Hi guys, I hope some of you guys are selling your bots on online that requires proxies. And im 100% sure that you all are going through a deep shit with the blacklisted & dead proxies issues. As a result software not work. But till then i figured it out that proxies are 3rd party object. But still clients dont want to understand that if the bot is not working or views drops its because of blacklisted

You are welcome. If you need any help just leave me a message here. Kindest regards Totolcs

I am late to the show on this, but it is good information to have for anyone. When using any ubot built-in browser than 21, your bot will generate a file named cef_browser_log.txt in the ubot studio folder (inside your roaming folder). That file gets bigger and bigger as your app runs and eventually drags it all to a halt that results in a crash. So, you need to setup a call to delete that file every so often while your bot is running. For example, you can put it in it's own thread so that it gets triggered and then waits x amount of time, and fires again and so on, while the bot moves