Scrapebox Out of Memory with 4GB

I just started using my new dedi server with SB. It has a core i3, 4GB of ram and plenty of space on the HD, but simply using fast-poster on a list that has 200,000 links results in an "out of memory" error and crash about an hour later. Do I need more than 4GB of ram for that many links?

Hmmm, That's plenty of ram to play with. Looks like SB is leaking memory. Email the developer regarding this issue.

BTW, how many threads are you running?

Same thing happening to me here. It "runs out of memory" if I go through large lists.

Since Scrapebox is a 32 bit application it's limited to 1.8 GB of memory space it's assigned when loaded. Over time as you load/unload lists this memory is not fully re-allocated resulting in a smaller portion in the original 1.8 GB. Keep an eye on the Memory Load/Memory Free statistic on the bottom as you begin to work through lists, over time this will degrade ESPECIALLY with lists over 250,000 URLs in size.

Best to work in chunks of 500,000k blasts. Then reload SB. Make sure to save an Application Enviroment inside Scrapebox and it takes just a few seconds to reload.

if you work over 250k urls it fails. also happened to me. this fail issue is happening when finalizing the software. i mean when blasting finished. it is really annoying actually.

Are you sure you are not running other high memory eating programs along with SB?

ILoveCSharp said:

if you work over 250k urls it fails. also happened to me. this fail issue is happening when finalizing the software. i mean when blasting finished. it is really annoying actually.

Click to expand...

This is not a hard-set rule. Mine dies somewhere over a million.

N

Hmmm strange, I run around 5 instances and I have had them post at least 100,000 lists and not ran into this problem.

Maybe that's the solution? Try different instances?

TheMatrix said:

Are you sure you are not running other high memory eating programs along with SB?

Click to expand...

Yup, the dedi is only running SB. But as the poster above you said, it could be that since its a 32bit application it only gets 1.8GB initially. Over time it fails to get the 1.8 back after each use so you have to reload SB. Ill start reloading SB and let you guys know how it turns out.

Also, with the link checker I noticed that it will check a series of links (thread count) and freeze for a minute or two until going on to the next one. I know my timeout settings arent that high. Is this another memory issue that can be fixed by reloading SB?

I also noticed that the standalone link checker that SB offers on its website will say "NOT FOUND" for a majority of the links if it takes longer than a few seconds for the page to load or if the link is very far down the page. Anyone else get this?

Got another out of memory and all I did was try to fast post a 62,000 list -_-