Extremely Elegant Solution To Rising Browser.exe Memory

[Frank 177]

Ok guys,

 

I wish I could say that I'm a rocket scientist in regards to the solution I've come up with but I'm not. I was wanting to clear the browser window if a user kills automation sequence, so I just did a simple 'load html()', with no contents to clear the visible browser window.

 

I kept running into the browser.exe climbing in memory as time tickers on if the user doesn't do a kill, so I thought, hmmm what happens if I just do the command before every new sequence.

 

Guess what! I completely clears the memory on the active browser.exe command each and every time. Literally down to 0 and it comes back to about 10mb of used memory!

 

Give it a try and report back!!

 

Frank

[HelloInsomnia 1103]

Well that's interesting, will give it a shot!

[Frank 177]

I've already had a few requests for more info, so I created a video for your viewing pleasure.

 

tickets please!

 

Hah, enjoy: http://screencast.com/t/Hpwk0DrHiBu

 

Frank

[Bot-Factory 602]

Did someone already try this method from Frank?

 

 

Dan

[vendeta30 4]

thanks

[BoosterBots 23]

Very nice! I will do some testing as well, looks like this is a solid simple solution here.

[RickBot0906 10]

Wow thanks Frank, I can't wait to give it a go tomorrow. It's been 2 weeks since I really slept well, this may cure that. +1

[RickBot0906 10]

Ok guys, here is my test results.

 

1. Laptop with .Net framework 4.0.0 Windows 8

Load blank html seems to do the trick. Memory level is stable and stays low not to crash the browser.

 

2. Desktop with .Net framework 4.5.2 Windows 7 Ultimate

Load blank html command crashes the browser. (Actually asset://asset window loads correctly on the first run of the loop but you get the "oh no your browser crashed") message every time after that. Currently trying to roll back to 4.0.0 for desktop to work.

 

I think Frank is on to something because it seems the navigation command is causing the memory leak, and as long as you have few navigation commands in a loop, you are essentially screwed. I have tried "close page" command also crashes the browser on 4.5.2. 

 

So far the only reliable solution across all different .net framework versions is to change agent, however that will break your session which will require you to log in again.  

 

Clearing memory is only a temporary solution as browser windows will eventually crash anyways, just takes a longer time. Not a good way to solve this issue.

 

So in conclusion I regret upgrading to Ubot 5.7, I should go back to 4.0 where I never imagined I had to deal with all these problems with just a 25 loop simple bot. If this issue is not solved soon, I don't see Ubot lasting in this environment. 

Edited September 29, 2015 by RickBot0906

[RickBot0906 10]

Ok guys, an update to the issue I was having.

 

Frank's solution does work very well indeed. All you need to do is to add navigate to www.google.com or something, then load blank html command. If the order was reversed it will crash on certain version of .Net but not others.

 

So make sure you add navigate to page first before using load html

 

: )

[webpro 31]

Will try this right away

 

THANKS FRANK!

 

 

 

edited:

 

hOW THE HECK DID YOU COME UP WITH THIS ONE LOL!

So simple!

 

Now i'm trying to figure out when to trigger this on multithreaded bots.

Probably in the begining of each loop i guess ?

[runsoftware 14]

I think i saw this being shared here before and it works nice but i never tested it on any big bot to be sure

[webpro 31]

I'm also trying this:

ui drop down("Headless","On,Off",#headless)
set headless browser(#headless)
allow javascript("Yes")
allow css("Yes")
allow images("Yes")
allow flash("Yes")

Seems to be doing great too!

Well at least it's not crashing all of the time...