Jump to content
UBot Underground

[Sell] Ustrap - The Best Drag & Drop Interface Builder For Ubot Studio! Now Only $97! - Super Fast Application | Bootstrap 3.0 | Built With Nodejs


Recommended Posts

Hello Carl, my name is Emanuel and firstly I would like to congratulate you for the excellent work with Ustrap so far ... I have been your client since 2015 when I acquired SSUB v5, and both have already helped me a lot in some projects ...

 

Recently I am developing a bot that requires continuous operation, since in general it monitors some situations and needs to stay days on. I am developing the GUI in the USTRAP and 10 days ago I came across a BUG in Ustrap that took me a week to find out what caused this BUG.

 

This BUG causes a kind of memory leak in browser.exe. it occurs when we use the component called by you of "Select" known as dropdown. This component has the attribute "Dynamic" which when checked causes the memory leak. this leak is a very serious situation especially for those who develop bots that monitoring that need to stay connected days. This bug causes the Browser.exe process to consume more than 1gb of memory over the hours and then crashes, freezing the GUI that does not perform any further action.

 

already tried to use two plugins that give "purge" in memory, but without success, because soon the process picks up the exact amount of memory that has accumulated so far, and from there it continues to rise more and more.

 

I took the liberty of recording a video to show you everything happening, logically at fast speed and skipping parts, because the bug is cumulative and gradual.

 

 

Video link: 

 

files used in the test: https://we.tl/t-rZYjmMqIQg

 

 

...I will also send you my GUI file which shows that only with it the BUG occurs, requiring no ubot code.

 

I use version 5.9.55 of Ubot developer, with USTRAP 2.1.0 .... the bug occurs in both chrome browser 21 and 49, bot being compiled or in build mode.

 

I hope this BUG is not difficult to fix, because my project depends a lot on this component, to the point of making my project unviable if it is not fixed

 

Thank you for your commitment to make our Ustrap more and more perfect, and you can count on me, whenever I find a BUG I will be reporting to improve this useful tool even more!

Edited by Emanu2000
  • Like 2
Link to post
Share on other sites
  • Replies 446
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Version 2.0.5 Update   - Added: Theme Builder - You can now create completely customised themes!    Video Demo:     Hope you like! :-) 

LOL! 147 bucks with 30% off is a slap in the face to owners of the software that you abandoned along with them. So much for a "big" discount... Good luck bloodsucking this already tiny community dry,

Its my birthday today! So lets celebrate with a great update!    Version 1.1.2 Update  Change Log:   – Fixed: Modal Scroll issue fixed on small windows. – Fixed: Checkbox (style 2) default state not

 

Hello Carl, my name is Emanuel and firstly I would like to congratulate you for the excellent work with Ustrap so far ... I have been your client since 2015 when I acquired SSUB v5, and both have already helped me a lot in some projects ...
 
Recently I am developing a bot that requires continuous operation, since in general it monitors some situations and needs to stay days on. I am developing the GUI in the USTRAP and 10 days ago I came across a BUG in Ustrap that took me a week to find out what caused this BUG.
 
This BUG causes a kind of memory leak in browser.exe. it occurs when we use the component called by you of "Select" known as dropdown. This component has the attribute "Dynamic" which when checked causes the memory leak. this leak is a very serious situation especially for those who develop bots that monitoring that need to stay connected days. This bug causes the Browser.exe process to consume more than 1gb of memory over the hours and then crashes, freezing the GUI that does not perform any further action.
 
already tried to use two plugins that give "purge" in memory, but without success, because soon the process picks up the exact amount of memory that has accumulated so far, and from there it continues to rise more and more.
 
I took the liberty of recording a video to show you everything happening, logically at fast speed and skipping parts, because the bug is cumulative and gradual.
 
 
Video link: 
 
files used in the test: https://we.tl/t-rZYjmMqIQg
 
 
...I will also send you my GUI file which shows that only with it the BUG occurs, requiring no ubot code.
 
I use version 5.9.55 of Ubot developer, with USTRAP 2.1.0 .... the bug occurs in both chrome browser 21 and 49, bot being compiled or in build mode.
 
I hope this BUG is not difficult to fix, because my project depends a lot on this component, to the point of making my project unviable if it is not fixed
 
Thank you for your commitment to make our Ustrap more and more perfect, and you can count on me, whenever I find a BUG I will be reporting to improve this useful tool even more!

 

 

Hi Emanuel, 

 

Thanks for reporting this bug. I will work on this right away and get an update out for the fix ASAP. I am sure I will be able to come up with something. 

 

Carl 

  • Like 2
Link to post
Share on other sites

Version 2.1.2 Update - (Skipped)

- Bad build :-(

 

Version 2.1.3 Update:

Fixed: Custom CSS changes not been applied to preview window.

Changed: Exporting files to folder is now 100x faster.

Updated: Select component plugin, also changed how select component works with ubot. Much better now. 

Fixed: Memory leak with dynamic select component, the UBot browser will still eat some RAM but much slower. This is not due to the component just the browser itself.

Changed: Modal backdrops are now hidden by default.

NOTE: There are still issues with UBot Studio 5 memory leaks. UBot Studio X is a little more stable by the looks of things, but memory still climbs slowly. I will report the bug to UBot team and hopefully a fix. 

  • Like 1
Link to post
Share on other sites

Version 2.1.2 Update - (Skipped)

- Bad build :-(

 

Version 2.1.3 Update:

Fixed: Custom CSS changes not been applied to preview window.

Changed: Exporting files to folder is now 100x faster.

Updated: Select component plugin, also changed how select component works with ubot. Much better now. 

Fixed: Memory leak with dynamic select component, the UBot browser will still eat some RAM but much slower. This is not due to the component just the browser itself.

Changed: Modal backdrops are now hidden by default.

NOTE: There are still issues with UBot Studio 5 memory leaks. UBot Studio X is a little more stable by the looks of things, but memory still climbs slowly. I will report the bug to UBot team and hopefully a fix. 

 

Hello Carl, I have already done some tests and the speed of the memory leak continues at the same speed :( ... I forgot to give you an important detail ... the speed of the leak is directly connected to the amount of components used ... in the test of video, I did with 12 selects, all with the dynamic checked and with the two variables filled ... using 12 selects Browser.exe grows on average 20 mb every 10 minutes ... in both chrome 21 and 49

Link to post
Share on other sites

The export of the Ustrap files really got much faster, great work ... just not loading my theme, I pointed to my .bot file as usual, but it seems to load the default theme when I import the UI code html panel .... something changed about it Carl?

Link to post
Share on other sites

Updated: Select component plugin, also changed how select component works with ubot. Much better now. 

 

 

Is this an update with the plugin? if yes, I got no plugin updates.
Link to post
Share on other sites

Hi Carl, would it be possible in ustrap to load an image dynamically? the SRC attribute can receive a variable of some form ?, with that we could change the image at execution time in the bot ... that would be fantastic!

Link to post
Share on other sites

The export of the Ustrap files really got much faster, great work ... just not loading my theme, I pointed to my .bot file as usual, but it seems to load the default theme when I import the UI code html panel .... something changed about it Carl?

 

After 2 days, I have finally found the memory leak!! UStrap is currently compiling and an update will be out shortly! :-) 

  • Like 2
Link to post
Share on other sites

Hi Carl, would it be possible in ustrap to load an image dynamically? the SRC attribute can receive a variable of some form ?, with that we could change the image at execution time in the bot ... that would be fantastic!

 

Will get this added, you would have to either use a image from a server url or base 64 encode the image first as a data url. 

 

I have requested this feature here: https://tracker.ubotstudio.com/issues/1262to load files from the local file system. 

 

What you requested is already possible using the Custom HTML component. Use this HTML:

<div variable="#image" fillwith="innerhtml"></div>

And set your variable with the HTML: 

set(#image,"<img src=\"yourimage\"/>","Global")

If UBot updated there HTML Panel some more, so much more could be done. Simple things like changing attributes by variables. 

 

For example, something like this would be nice, if it worked!

<img src="" variable="#image" fillwith="src"/>
  • Like 1
Link to post
Share on other sites

 

Will get this added, you would have to either use a image from a server url or base 64 encode the image first as a data url. 

 

I have requested this feature here: https://tracker.ubotstudio.com/issues/1262to load files from the local file system. 

 

What you requested is already possible using the Custom HTML component. Use this HTML:

<div variable="#image" fillwith="innerhtml"></div>

And set your variable with the HTML: 

set(#image,"<img src=\"yourimage\"/>","Global")

If UBot updated there HTML Panel some more, so much more could be done. Simple things like changing attributes by variables. 

 

For example, something like this would be nice, if it worked!

<img src="" variable="#image" fillwith="src"/>

 

Carl, you're a genius! thanks! ... is a tip for those who do not want to use an external URL, you can convert your image to base64 and insert directly into the variable as Carl suggested, it works perfectly!

Edited by Emanu2000
Link to post
Share on other sites

Version 2.1.5

Finally found and fixed the UStrap memory leak, should be nice and stable now! - This seems to be a UBot Browser issue not a UStrap Issue.

Fixed: Custom CSS imports getting duplicated.

Fixed: Selected theme not getting imported/exported.

Link to post
Share on other sites

Could you post a tutorial on how to use it properly?

 

Please see attached file for a tutorial, this file was used to test the memory leak. 

 

The bot will load 300 items into 16 Select Components via the custom "Ui Loaded Event Define".

 

Thanks!

Memory Leak Test.ubot

Link to post
Share on other sites

Please see attached file for a tutorial, this file was used to test the memory leak. 

 

The bot will load 300 items into 16 Select Components via the custom "Ui Loaded Event Define".

 

Thanks!

 

No, I was talking about this:

 

http://network.ubotstudio.com/forum/index.php/topic/21603-sell-ustrap-the-best-drag-drop-interface-builder-for-ubot-studio-now-only-97-super-fast-application-bootstrap-30-built-with-nodejs/?p=136113

 

Is it about loading a list dynamically into a Select component - behavior changed?

Link to post
Share on other sites

 

Ohh ok, no, no change.

Link to post
Share on other sites

Please see attached file for a tutorial, this file was used to test the memory leak. 

 

The bot will load 300 items into 16 Select Components via the custom "Ui Loaded Event Define".

 

Thanks!

 

Hi Carl, can you tell me how you did the tests, was it just in Ubot X or in 5.9 or both? ... because here for me is still occurring memory leak in the same way, at the same speed .... I use ubot 5.9.55
 
Tell me how you did your test? How long did it leave open? because in the beginning it tries to stabilize, it makes some returns in RAM, but then it starts to jump
Link to post
Share on other sites

Ubots UI browser.exe has a memory leak it kills any bot after a set amount of time depending on the size of your UI and the amount of images ect 

 

 

I found if you use OS free memory command and set it on a loop to run every 60 sec while your bots running this keeps your UI stable by clearing the browsers.exe memory 

 

 

i have had bot running for weeks like this 

Link to post
Share on other sites

Ubots UI browser.exe has a memory leak it kills any bot after a set amount of time depending on the size of your UI and the amount of images ect 

 

 

I found if you use OS free memory command and set it on a loop to run every 60 sec while your bots running this keeps your UI stable by clearing the browsers.exe memory 

 

 

i have had bot running for weeks like this 

 

Also I am using a plugin that does the purge in memory every 10 seconds, it seems to me to work better with bots that have memory leak by scraping, with many sequential loops. In this case, bot leaks the memory simply stopped, just containing the ustrap interface in the Ui html panel, and containing the select component with the active dynamic attribute, and the more components there are, the faster the leak.

Link to post
Share on other sites
Hi Carl, I'm sorry I only bring problems ... but I'm at full steam on a project and I can not stop now, what I found today is that the "display component" command of the Ustrap plugin stopped working after the last Ustrap update (2.1.5) ... without it my project is stopped.

 

If you have how to send me the 2.1.0 and 2.1.3 versions in the meantime, I will thank you very much!

Edited by Emanu2000
Link to post
Share on other sites
This happens because since version 2.0.9 you can trigger a define when loading the UI html made in ustrap

 

"" UI Loaded Define "option to Import / Export settings, here you can set a run to when the UI has finished loading."

 

probably your UI is calling a define that does not exist in your .ubot code

 

you just leave the field "UI loaded Event Define ():" blank this error will not appear

 

 

n35cuOO.png

Edited by Emanu2000
Link to post
Share on other sites
Hello Carl, I made the last update 2.1.6 (although it was not announced)

 

... let's go to the results

 

The "display component" command returned to normal operation

 

Memory leak due to "Dynamic select" still persists

 

A new problem appeared, I believe that because you are repairing the select component, it is now no longer dynamically updating the values of the variable list, besides the pre-select is also not working ...

 

see the video below:

 


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...