Scrapebox crashing - Possible Fixes and Solutions

[loopline]

how do you increase your tmp folder size?

Open IE Go to tools-> Internet Options -> (Content Tab) -Browsing History settings -> Temporary Internet Files

Adjust to 1024 or whatever you want that is larger then what its set on.

 

[G0D0VERY0U]

Currently on a scraping project. Scraped over 6 Million urls and counting. It saves the ones over 1M to files increasing by number. How much RAM do you have? Whats your processor? I had a lot of issues with it freezing harvesting and posting when I didn't have a good enough machine to run it on.

What kind of crash are you getting?

Okay, not to be a hardware bragger but hardware is certainly not the case for all of us, specifically me.

If SB is crashing because my i7, 9Gb DDR3 box can't support it - then I don't know what would.

You must have some kind of water cooled, plutonium powered, self aware mini-skynet over there.......

 

[-Jericho-]

Open IE Go to tools-> Internet Options -> (Content Tab) -Browsing History settings -> Temporary Internet Files

Adjust to 1024 or whatever you want that is larger then what its set on.

Just FYI:

In IE 7 it's under the Internet Options -> General -> Browsing History (settings) -> Temporary Internet Files

I just upped mine to 1024 to see if it helps with crashing since I can never seem to get through slow posting without it crashing.

 

[G0D0VERY0U]

It should, I found that helped reduce my crashing by about 75%.

I'm now playing with all of my cache settings to see if I can find some sweet spot for SB. Unfortunately, I'm working with a Vista box which ... well.. do I really need to say much else when it comes to memory handling and operating systems? Vista = Epic Suck.

I do want to point out a bit of irony for us guys who do spam like it our job.
- Do any of you Xrumer owners see the irony is having xrumer which now can't scrape (as it is out of the box that is), and SB - which now can't post without crashing. It's like a person without legs being paired up together with a person that has no arms to make a complete human.

Hint hint, nudge nudge.....

(Use them in conjunction to make one complete program)

 

[-Jericho-]

I just updated to the newest version and now I can't even get into SB without it crashing. It's running through harvester crashdump when it glitches out. I then get this error:

Access violation at address 00583A89 in module 'scrapebox.exe'. Read of address 0003FFFC.

Anyone else getting this?

 

[EagleRose]

Yep - got the same thing last night.
Did a search on G to find what that means. It means that SB tried to use memory that was already in use, causing the error and crash.

Before, I was crashing at post 250 in the slow commenter, this time I made it to 350. There is progress.

Thinking about moving SB to a new machine and see what results I get from there. A stand alone machine, that I just built.

 

[G0D0VERY0U]

I'm thinking that a script which cleans your cookies/tmp files every 30 minutes may help. Sure, you may loose whatever blog SB is working on at the time, but overall there may be a stability benefit in it. I'm noticing after about 450mb of tmp intnet files build up that SB begins to really slow down and then hit a "Crash zone."

Anyone know of such a unicorn? I don't think there has ever been a need for one, but it's the most likely answer for several of us.

And for the record, .43 doesn't crash any more or less for me than .42,.41,.40 etc did.

 

[proxygo]

no problems programme
works fine here . fast as ever - no issues
cant say ive had any issues at all since the kind owner
gave me a copy - excellent work - with 0 problems -
all good here

 

[G0D0VERY0U]

It's a great tool, no question. I hope nobody thought this was a thread to "Bash" scrapebox. Just the opposite really - it's to help spread understanding on how to make it run it's best.

That having been said, what modifications or setting adjustments have you made to your windows OS that enables it to run so well? Hopefully more of us can try them, to repeat your success.

 

[pyronaut]

I don't own scrapebox, So I cannot be 100% sure. But, using the mshtml DLL, what is likely happening is that SweetFunny is using a browser on the backend (Which you guys have more or less confirmed).

When I was selling my own commenter, there is a big big issue with Javascript popup windows. Like those ones when you try and leave a page and they say "Please don't leave blah blah blah".

AFAIK, these were near impossible to get around. And they freeze the browser (You can't navigate to a new page etc). It may be a completely different issue, but I know for a fact that was a problem. And you can't just disable JS either, because that is the whole point of using the slow commenter.

Unfortunately, I develop in a completely different language, so the two error messages cannot be compared. But I would be semi-sure, that this is a problem with Scrapebox (And likely will be near impossible to fix).

 

[-Jericho-]

I just updated to the newest version and now I can't even get into SB without it crashing. It's running through harvester crashdump when it glitches out. I then get this error:

Access violation at address 00583A89 in module 'scrapebox.exe'. Read of address 0003FFFC.

Anyone else getting this?

So my work around on this problem was easy enough. I had a copy of SB in another folder when I want to have two instances running.

I updated the copy to the newest version and it's working fine now. Think it has something to do with the harvester crash dump check which apparently is not on in the copy I'm using.

As for the errors with slow posting I was told to run the blog analyzer first to weed out the bad sites. That thing just takes too long.

I did run the alive checker addon a couple of times to weed out some of the dead sites which I don't usually do. We'll see if it makes a difference in glitching out my slow posting.

 

[-Jericho-]

How do I turn off the stupid security certificate popup?

I can't find where to disable it. All the settings I have turned off will not get rid of this aggravating popup.

 

[scriptkiddies]

i cannot run the proxy checker into scrapebox since 1.14.30

the proxy checker get blocked after the first proxy tested

anybody have the same problem ??

i reset all IE setting
but still get this problem

thanks

 

[scriptkiddies]

i cannot run the proxy checker into scrapebox since 1.14.30

the proxy checker get blocked after the first proxy tested

anybody have the same problem ??

i reset all IE setting
but still get this problem

thanks

 

[G0D0VERY0U]

I did.

You need to get EVERY POSSIBLE update for your OS and use the newest version of IE8. Fixed my problems

 

[G0D0VERY0U]

Hey guys - I just made an adjust to my systems virtual memory size and manual set the size to min 20000mb and the max to 50000mb.

Not sure if it will prevent crashing but it sure does let scrapebox run mcuh faster - even through proxies the timeout counter barely hits 9 before the post is either made or failed. That's awesome...

 

[-Jericho-]

And you can't just disable JS either, because that is the whole point of using the slow commenter.

Can anyone confirm this? I just checked a page that the slow commenter locked up on and the page doesn't load and I get a script error.

So obviously it is a script that's locking it up but is there a way to prevent the script and still have the slow poster work?

 

[pyronaut]

Can anyone confirm this? I just checked a page that the slow commenter locked up on and the page doesn't load and I get a script error.

So obviously it is a script that's locking it up but is there a way to prevent the script and still have the slow poster work?

I can confirm it!

There is many plugins for wordpress, that only allow comments when you receive a cookie. AFAIK, the cookie is given to you, when a piece of javascript is executed. When you use the "fast" method, it cannot execute javascript (It is just a simple web request). So you cannot comment on these pages, hence the invention of the slow commenter.

With BlogEngine, it runs on ASP.net. ASP.net is pretty much a wrapper for javascript anyway overlaying the basic HTML. Especially given that the comments are AJAX (Async Javascript ).

Put it this way. If we could turn off javascript with no issues. Then we may aswell just use the fast commenter.

 

[loopline]

sbox has crash recovery started in Version .45 and as of .47 its fully automated. so if it crashes it will restart and resume its self in slow poster. This should basically solve all of the problems listed in this thread. Generally speaking anyway, but there are certainly pc issues that can complicate things.

 

[-Jericho-]

WOOT! SB is asking me if I want to stop scripts now. I haven't had a lock up yet since I last updated. This is the longest slow commenting I've been able to do since I purchased it.