Please do not despair. Things like this have happened to all of us before, and ultimately we find a problem (usually ours).
The best advice I can give you is to set a breakpoint for crazy trace statements and hope that debugging goes through them.
As you said, you were looking for trace instructions, would it be possible for them to be on the action bar (timeline code)?
How is your code and .fla organized? Is everything in external .as files or is it built into the timeline?
And finally, do you perform some kind of reflection, for example getClassByName () (in as2 eval ("_ global." + ClassName))?
Also, to make sure that this is not a caching problem, copy only the .fla files and their associated .as files and move them to a new computer or to a new folder and compile it using another Windows user (assuming u 're, using windows), this should be enough to get rid of all caching crazy flashes.
source share