This is entirely false. Our support staff noticed errors with your code, suggested improvements, and once they were made, did not notice any errors.
That's the thing, after improvements were made and the issues were all still there. Even after being rewrote, everything still broke.
What you sent was an image of your computer running out of memory. That's not the same as finding a memory leak. It is possible to write code in UBot Studio (or literally any programming language) that uses up your computer?s memory, but from the image you sent, there was no evidence that the error was caused by UBot Studio.
I have the hardest time believing my gaming rig ran out of memory with ubot.. especially since I can run the most demanding games of today just fine with no memory issues and still have all my development programs running in the background. If it did, it was from a ubot leak - especially since I only ever got errors with ubot.
Not to mention I was testing on 4 different computers and an amazon cloud server..
There was no reason to escalate the issue, because the support staff could not reproduce your error. There was never a point where anyone stopped responding to you via support, as you can see in the ticket. No one ignored you. In fact, I (in addition to my staff) spent many, many hours trying to determine the issue with your script. I interacted with you directly on BHW. Please review your support ticket.
I have, in fact yesterday when you checked the ticket you'll see the last reply was my own. There in fact was a memory leak proven with the browser(screenshot was included of that, too), I wasn't the only one who posted about it I just didn't open a separate ticket because why clutter up so many tickets when I can consolidate all into one.
Cody,I did respond to you.
My last message to you was sent on 03-25-2016 at 08:57 AM and has received no reply - which is not needed now this post.
Nowhere did anyone stop helping, or say that the issues were reproducible, unfortunately. The last response from our support staff regarding your script was, in fact,
Just going to leave these replies from your staff here:
I have run your revised bot several times and I did encounter quite
a few errors just like you. I still think there are some coding issues
that you need to correct.
It is entirely possible that having coding issues like these are whats
causing memory issues that force UBot to shutdown.
Acknowledging both reproducible issues and memory issues with ubot - even if errors are being blamed on my code.
For shits and giggles I took the old, original script I was working with when I first opened the ticket and just ran it. What do you know, it works fine. Ran it 5 times successfully in a row, no issue. The only thing I've updated on my system is ubot, no windows updates, drivers, etc. That tells me the last update fixed whatever the issues were with ubot thus proving my point that it was a bug with ubot.
My code could have been the problem but that leaves a few things to question.
Why would a function work the first, second, maybe even third time then ubot fall on it's face the fourth? Or even the first, second, and third - it was all random when it errored out.
Why would ubot allow me to set a specific scrape function using all the built in functions and show the proper results in the scrape window but not allow me to edit that function because it tells me it was invalid and couldn't find anything but when the script hit that specific part it worked and grabbed a variable just fine?
I'm not here to bash ubot, in my career I don't have time for BS like that. I think it is a great piece of software that has worked well for many people. It does have a great interface and there's a lot of information on it out there. It has saved me from having to dive into python because (I thought) ubot would have been faster and easier. I just wish my findings would have been handled another way rather then constantly saying "it's your code" when screenshots and ubot bug logs prove otherwise.
