Flash8 memory issue...
- Started
- Last post
- 15 Responses
- mrock
hi,
not sure if this is the right place to ask but any leads would help. I'm currently trying to debug my actionscript using the Flash 8 built-in debugger. The app halts and returns "Flash is out of memory", and have 2GB of ram on my machine. My other alternative would be to use "trace" statements, but that's so overkill. Thanks for any help you can provide or for even pointing me to the right forum.
- maximillion_0
if you have embedded video you can get this error - or too many images etc. try dynamically loading heavy content
- mrock0
yeah it's pulling info from an xml feed that's huge. That might be part of my issue. Thanks!
- joyride0
it normally handles large xml files pretty good. I've seen this before with on open for loop.
- Mimio0
Could some filters or an array is way too large for the constructor you're using. This is all in AS2 right?
- skt0
so does the debugger actually work these days? never gone back to it since flash 5 as it was shite then. just trace everything out these days.
- PonyBoy0
someone mentioned a 'for' loop that could be out of control...
... that was my guess too - are you parsing through your xml w/a 'for' loop?... that'll shut you down fast if the for loop doesn't have a reason to stop...
... i've never had memory issues w/massive amounts of video/data embedded etc... but yeah - a good practice would be to get the embedded video pieces and as much of the graphics out of your authoring file and pull that all in dynamically too...
... as far as the debugger - I've never really seen a need for it as I don't build massive applications... so I can't help w/the debugger... :(
- Mimio0
It could be a lot of things. If you have BitmapData objects stored in constructor function variables. You have to dispose(); of that shit.
- mrock0
Actually all it's grabbing are flat images from a server somewhere through an xml file. The xml is huge, 130 main nodes with about 83 child nodes, so that X how many it loops (you do the math). Of course when I run it without the debugger it's fine. Presently I'm doing the trace statements but I was hoping on a faster solution. The built-in Flash debugger can't seem to handle the load. Thanks for your assistance so far.
- myobie0
isn't there a limit for the xml parser?
i think it's like under 40k or so.
this bit me once.
- mrock0
not sure. Finding out now.
- maximillion_0
create a text field and use that to output the info yr looking for - this is what i do instead of trace
- mrock0
ah yes! Thanks max-a-million. That help somewhat.
- gdodds0
X Ray Debugger can be very useful for debugging flash issues, and it lets you test with your files online (in the browser). Worth taking a look at :
- mrock0
looks promising. I'll check it out, thanks!
- monNom0
I heard somewhere that flashplayer limits it's memory allocation to 32Mb.
make sure you throw stuff away after you're done with it:
delete objectName;