Getting Absolutely Hammered With Cef Crashes

[Brutal 164]

I'm getting absolutely hammered with cef# crashes.

 

I don't see anyone else talking much about it so I assume its local to me.

 

 

I am using the "system free all memory processes plugin, I am even getting crashes when I just open the bot in the editor without even running yet. The image i attached was a fresh open while I was just trying to compile the bot.

 

Any ideas?

[videoseomkting 1]

You are not alone. I am also getting those crashes with browser 39 regardless of the plugins I use.

[cүвεя_נυηкιε 68]

I'm getting absolutely hammered with cef# crashes.

 

I don't see anyone else talking much about it so I assume its local to me.

 

cef.PNG

 

I am using the "system free all memory processes plugin, I am even getting crashes when I just open the bot in the editor without even running yet. The image i attached was a fresh open while I was just trying to compile the bot.

 

Any ideas?

 

 

Same here i havent been able to use 39 since it was available, 

although to be fair i tried the latest UBot update yesterday (V5.9.11 I think) and it was a little better, 

captcha images were downloading normal for the first time,

but with 39 enabled eveything takes like 2-5 seconds slower to process and then crashes

 

I figured things would be resolved eventually and V5.9.0 suits me just fine for now

 

 

 

CJ

[Brutal 164]

Thanks guys - I'll swap to 21 and see if it helps.

[jason 101]

Are you able to narrow down specific commands causing any crashes so we can take a look at them? If so, please put in tracker. Thanks!

[Brutal 164]

I haven't been able to isolate anything - It is very random.

 

I have now swapped over to 21... and it is presenting it's own set of problems!

 

On the other hand, if it was brain-dead simple, everyone would produce complex bots and the market would be financially crushed, so I don't mind fighting a few battles.

[cүвεя_נυηкιε 68]

Are you able to narrow down specific commands causing any crashes so we can take a look at them? If so, please put in tracker. Thanks!

 

 

Hi Jason

I can safely say that the latest update fixed the image downloading that i mentioned in another thread,

but still noticeably slower when executing anything, 

 

It is quite random at my end but i can say that when i use the "Headless" node in a "New Browser" using 39 then a little bank window will open and stay there for about 3-5 seconds,

but further more the process/s running inside decide themselves if they are going to work or not, its a bit weird :/

 

and this is the same depending on how many threads are running, 

 

for example, .. 

I have a multi-threaded bot that will run with or without a browser using the the Headless feature, 

if i set the threadcount to 10 then 10 little windows will open and wait for the 3-5 seconds, then when they eventually dis-appear only like 6 of the 10 will actually do anything, 

and really all they are doing at the start is setting a user agent then navigating to a webpage,

 

 

if i switch back to 21 then i "might" see a split second flash of a page but you wouldnt know it was opening any windows, 

and all 10 threads will continue their procedure without any problems.

 

 

 

I know your right I should report to the tracker, but in genuine honesty i lost all concept of time since my site took off, there are literally not enough hours in the day,

when im working on a project i pretty much slip into a coma until my wife calls me for food LMAO

so its not that i dont want to, its more the thought of submitting, creating an example, working through it, trying things to resolve it etc etc etc .. when i can just find a way around in a couple of mins to a few hours.

 

 

and also ive had a peek at the tracker and its usually only a matter of time until someone with the same problem submits, 

im a patient guy, good things come to those who wait and all that

 

 

 

 

CJ

[PRO 69]

I recently also have had same described random "Cef Crashes" with Chromium 39.

 

Had this errors when executing "running" various scripts from the botbank.

 

I can not tell how to reproduce this effect however.

[Brutal 164]

I ended up just moving to 21.... I know that eventually the other one will be stable.

[cүвεя_נυηкιε 68]

I ended up just moving to 21.... I know that eventually the other one will be stable.

 

my thoughts exactly, 

21 suits me just fine until that momentous day arrives, .. 

 

and i reckon when that day comes it will be BIBLICAL !

 

 

 

 

 

 

 

I recently also have had same described random "Cef Crashes" with Chromium 39.

 

Had this errors when executing "running" various scripts from the botbank.

 

I can not tell how to reproduce this effect however.

 

 

Yes i find it the same at my end PRO, 

some commands take ages to run, then dont run at all, ... then crash

 

the only issue i can replicate consistently is if i use the Headless control, 

no matter how i use it there is a noticeable pause/delay before it decides if its even going to run on this occasion lol

 

 

Just in case anyone is reading this and experiencing the same sort of issues, .... (and you dont have any hair left to pull out )

 

personally I have found that 5.8.5 is the most stable, quick and responsive ... (at my end anyway), 

however, 5.8.5 doesnt have the Headless feature so im using 5.9.0 which is "almost" as smooth and does have the Headless, 

 

I cant stand having to wait longer than 1 second after clicking/running something, ..

mainly because my PC is a bit of a power horse (i7 - 64GB RAM) so shouldnt run into this sort of stalling/lagging,

 

so if you just cant get along with the latest version just download an older version for the time being, 

UBot will fix it they always do  

 

 

 

 

CJ

[jason 101]

Sounds like some reproducible stuff in there that we'd love to see in the tracker ! 

[Brutal 164]

Jason I don't really know how reproducible it is.

 

In my case, I could be running the script and the browser would just crash. Sometimes it would give an indication (like the visible browser in the editor would become completely unresponsive), while at other times the browser may still allow you to physically change urls but would not respond to program commands.

 

To make it even more elusive, the break point was never the same. You might run it through perfectly on one go, and on the next it might hang at absolutely any point along the process.

[Brutal 164]

Here's an update.

 

Out of the blue, for some reason today my ubot editor (well, not the editor but the code being run) randomly went unresponsive.

 

I tried all of the usual stuff - It kept happening.

 

So in a frustrated last attempt I changed back from 21 over to 39

 

The cef almost instantly crashed, yet the program continued to run (opposite of what it was doing previously) - So I just let it continue to run.

 

Low and behold - it's running smoothly

 

Man this is so confusing

 

I originally built it using 39 .... kept crashing and going unresponsive

 

changed to 21... started acting right, so i continued building with 21

 

today, using 21 it kept going unresponsive so i switched to 39 and now it's smooth and responsive.

 

I hate running my bots in the editor, but because of the erratic behavior I am forced to run it in the editor just so that I can change back and fourth from 21 to 39 as needed.

 

This would be basically ok if i was just running my stuff locally, but I don't. I tend to sell what I build, but can't in this case because it would turn into a support nightmare that could destroy my online rep.

 

Having said that - Understand that I'm not complaining about mean-ol-ubot... I'm simply voicing frustration at the fact that my bot seems to change its mind on a day to day (hour to hour) basis about which browser it is willing to work with.

[PRO 69]

Just a "stupid question" @Brutal:

 

Can the usage of exBrowser prevent such crashes? If so, are there any known downsides using exBrowser as an alternative?

 

Wonder if you can tell. Sorry for slightly off topic.

 

Thanks!

[Brutal 164]

Pro, I do have the ex-browser plugin but have not used it before so I really don't know how it would perform or if it would help to alleviate this issue.

 

If I try it at some point, I'll let you know the end results.

[HelloInsomnia 1103]

You should ask Dan about that he will be able to tell you if it will prevent the crashes, I think that it probably will but he would know for sure.

[webpro 31]

Why, but WHY! I always forget to use another browser if i get lots of crashes LOL!

 

 

Thanks for reminding me this guys.

 

 

By the way, if you are reading this and wondering how to switch browser:

1) Go under TOOLS menu at the top of UB

2) Then OPTIONS

3) Select 21 in the Browser pull down menu, instead of 39

[webpro 31]

Crapppp

I talked too fast!

 

It's crashing all of the time.

Now i can't pin point the problem. So i can't create a tracker ticket so that the crew is able to troubleshoot it.

 

Right now i suspect some DEFINE commands?

If i run the nodes one by one, it works perfectly....

 

I'm on Windows 10

Using 5.9.13

[juicehunter 30]

Why is ubot still at 39 when CefSharp is at verion 47.0.2 and fixed already a ton of issues between those versions.

[webpro 31]

Hummmm maybe that would help a lot?

[Evernano 2]

Just my two cents guys... i was having same issue but some others... i am running windows 10... I ended up reseting windows 10 fresh on my computer and Re downloading ubot again, All my problems went away.... no more crashes here.. every thing is working fine... I not sure if this helps you but it worked for me....

[webpro 31]

Well well well

Windows 10 here also and i'm pretty sure all the glitches started when i made the switch!!!!!!!

[videoseomkting 1]

I gave up trying to use Chrome 39 some time ago. It has crashed to me with Windows 7, 8 and 10, so I don't think it is an issue with the Operating System.

[brusacco 20]

I dont get crashes, but in a fresh Ubot Studio screen, navigate to a FB group and upload a picture. The Browser gets unresponsive. Latest Ubot, Windows 7 and Windows 10. Chrome 39.