I think the error console might be a source of memory and lagging errors

Question

I notice that if I open the Firefox Error Console logs that the error listings are fast and frequent (which is okay if the browser is working past them). However, after using Firefox v2 and upward I am now pondering if the error log might be the source of the hard-to-kill lagging and memory issues. I note that as the longer Firefox runs, the longer the error log must grow as well as the number of page fault calls which all eats up memory or requires more frequent disk swap paging to record it all. The longer it all runs, the bigger the error log goes.
Since the error log probably gets more leeway on memory cleanups and CPU hits (to retain accuracy) this eats up more processor time and more hard-to-kill memory space, which then kicks in the system's Paging File causing more disk swapping.
My suggestion is simple, create an ABOUT:CONFIG option to, clip off the error log once 100 (or user-defined) errors are hit. Delete the oldest errors, keep the newest until they get pushed off the rotating stack. Obvious problems with this are first renumbering rolls (deleting 001 and changing 002 to oo1 and so on also eats up pointless CPU cycles). Having an ever-growing numbering stack would hit an out-of-bounds error eventually (delete 001, number latest error 101, and so on).
A rotating "ERROR ROLLOVER LIST POSITION MARKER" is simpler.
Just have a variable called "ERROR LIST ROLL MARKER" and it holds a variable of 001 to 100. Whatever numerical value of the "ERROR LIST ROLL MARKER" is marks where the text value of the error listing is named "ERROR LIST ROLL MARKER".
Let us use for example that the last error on the rolling error list was at position 087
Text value for error list position 087: [ reference to undefined property ]
The value of numeric variable "ERROR LIST ROLL MARKER" would be 088
The text value for error list position 088: [ ERROR LIST ROLL MARKER ]
When we get the next new error, the variable numeric value of "ERROR LIST ROLL MARKER" would become 089
The text for error list position 089 would become: [ ERROR LIST ROLL MARKER ]
The text value for error list position 088 would become the text of whatever the current error was.
In this manner you can keep a simple quick list, save a bundle of memory, and in the event of a crash, you look for ERROR LIST ROLL MARKER values and you know exactly what the last error was and the 99 that preceded it.
When the ERROR LIST ROLL MARKER hits 100, then you simply push that to the 001 location when the next error hits and after the next error, the ERROR LIST ROLL MARKER becomes 002 and that current error text overwrites the 001 location.

Answer 1

Hi, I managed to solve the errors (kind of) by using this code.
for (var i:int = tower1BulletArray.length - 1; i >= 0; i--)
if (tower1BulletArray.parent)
tower1BulletArray[l].parent.removeChild(tower1BulletArray[l]);
tower1BulletArray.splice(i, 1);
However, the problem still persists that the bullets stay in the screen after I change the scene. Any solution? Thanks!