This content has been marked as final. Show 6 replies
It's tough to speculate without seeing the code... but here's a thought. All variables in flash are Floating point numbers. That's nice, because the scope is huge, but not so nice, because they are often inaccurate in their math. Normally the inaccuracy is well below 0.000000001, but when you have variables that just keep going for days and days, those inaccuracies can grow on you.
If you have any variables that are getting continuously modified for days on end, try to split up the task so your variable gets created, does what it needs to, and gets deleted. This way your numbers won't screw up on you.
Then again, this may not at all be the problem you are running into.
Interesting... Each of my components is unloaded and reloaded every minute or so, I was hoping it was some sort of depth problem, but each time I narrow it down to something, I find that I've not only worked through that issue, but it doesn't match the symptoms anyway.
Seems like a constant looping and much CPU usage that your system may not handle that kind of load after 4 days of continuous run. If you're loading http images, possibility is your temp internet folder is cleared (either manually or via a schedule) and if you're communicating with server scripts, that could be another possibility.
I was wondering if it could be a CPU thing, or a flash app stability thing, but its not all the time that the red screen of doom appears, probably once every 3 images it pops up. Here is the psuedo of what happens...
"main.swf" loads XML of all background images, and their paths
"main.swf" loads "background.swf"
"background.swf" immediately loads a background image (random)
*wait 27 seconds while pan effect manipulates image (setInterval - not Tween class)
"main.swf" removes movieclip, and clears interval.
-rinse and repeat
Maybe I'll try to rebuild it using the tween class and see if I end up with the same problem.....?
Is this running in a projector or a browser? Have you tried the other?
If a browser could it be some kind of cache problem with the browser?
You mention removing movieclips and clearing interval. Do you also reload the XML? Do you clear it? (Not likely the problem, but were grasping here!)
What happens if you reduce the number of random images for the background.swf to load to one?
Also, I'm not really understanding what goes red. Can you post a screen shot? Or at least a shot of how it normally looks and then describe which parts turn red.
its running projector. --I have tried the other, but 4 days on a browser is too taxing.
I only load the XML for the images once.
When I drop the amount of total images, nothing changes.
when I drop the size of the indiv. images, nothing changes.
I'll see if I can get a screenshot up.