Purging Castmembers

[Mnementh]

Has anyone gotten this stupid error more than usual lately? I've gotten it at least once a day for the last week or so and today alone, I've seen the message 7 times!

 

[rickyratsmom]

Got that alot yesterday...then dc I think the site is just real busy when that happens.

 

[FruitFaerie]

Yeah I had that too. I thought it probably happened because of my Shockwave - everytime I update it, it does funny stuff for a day or two.

 

[Clarity]

I get it at least once a day. And the chances of it happening go way up if I'm in line for a host room.

 

[SweetJaydGrl]

I've been getting this everyday, and if I log off and back on then I get another popup message. So I have to completely shut down my computer system to make it go away. This is last nights message as I was going through a host room, thankfully I still got my pin.

 

[cteddiesgirl]

I just had this happen.

I was busy reading and doing stuff around the house and had my person running thru JC a lot and I didn't clean out my temp files.

Usually, if I keep cleaning out my temp files, I don't get this problem.

 

[ChipNDale]

I really do like that message its rather funny! But however i do not believe it is funny to receive that message.

 

[FruitFaerie]

Yeah I can't even get onto the site right now, it comes up saying
'Out of Memory: even after purging all purgeable cantmembers'
or something to that effect, so I'm leaving it for now..

 

[Melp]

I have gotten this more and more lately as well, usually seems to be when I am riding the dark rides over and over or had been running my titles through quests without closing my vmk pal windows. Closing the window after a character or two logging on and not switching rides alot seems to have made it better so far.

 

[cteddiesgirl]

I have gotten this more and more lately as well, usually seems to be when I am riding the dark rides over and over or had been running my titles through quests without closing my vmk pal windows. Closing the window after a character or two logging on and not switching rides alot seems to have made it better so far.

I usually just clean out my temp files while still logged in. It won't clean out everything, but it will clean out most stuff.

I also tend to clean out my files before logging in, so I start with a clean slate.

This does seem to work for me. I have gotten this message only once in over a week.

 

[Macca1111]

Maybe I need to do that today...it's usually not bad for me, but today it's kept me from getting in or functioning when I do manage to connect. Hmm...

 

[PirateBell]

I haven't gotten that at all that I can remember ..but I too clean out my files... all the time on regular bases..several times a day or more depending on how many mules I have on!

 

[SweetJaydGrl]

Well it just did it for me again, It usually happens daily. But this time after logging off, rebooting and deleting my files and cookies. I got this message. I've never seen this one before.

Anyone figure out why shockwave is doing this to some?

 

[Melp]

I usually just clean out my temp files while still logged in. It won't clean out everything, but it will clean out most stuff.

I also tend to clean out my files before logging in, so I start with a clean slate.

This does seem to work for me. I have gotten this message only once in over a week.

Thanks for the suggestion but didn't work for me today. I was logging on and off my titles to do credits and on the second one after clearing temp files it gave me the error. At the time I was not doing anything with any other sites or programs. I'll keep trying to see if it helps me over time but so far not so good

 

[Mnementh]

I just had this happen.

I was busy reading and doing stuff around the house and had my person running thru JC a lot and I didn't clean out my temp files.

Usually, if I keep cleaning out my temp files, I don't get this problem.

Thanks for the tip. I'll have to keep that in mind

As for that other message, SweetJaydGrl, I've never seen that one before. It's kind of odd and I have no idea where that could've come from.