[Solution] Runtime error #1025: An invalid register X was accessed

A while ago I was confronted to a very strange runtime error:

“An invalid register <number here> was accessed”

I was like “what the …”. I didn’t really understand, why this error suddenly showed up – reproducible. So I started digging around in my sourcecode.

After a while (few hours!) commenting, cutting, pasting code I found out 2 facts:

1. The error was in connection with some code dealing with XML
2. I could make the error go away by moving functions around in my code (simply moving a function from the end of the sourcecode to the top!?)

So I took a closer look at the XML thing.

As it turned out it was a problem with xml default namespace i had set up because I didn’t want to/couldn’t write the namespace to every tag I wanted to access. It looked something like this:

…

public function GetXMLResult(event:ResultEvent):void
{
var doc:XML=XML(event.result);
var ns:Namespace = new Namespace(doc.namespace());
default xml namespace = ns;
//some xml data extracting...
}

What was the solution to this strange issue (yeah, at some point even the code-moving-around-hack didn’t work)?

Adding one single line at the end of this funcion:

public function GetXMLResult(event:ResultEvent):void
{
var doc:XML=XML(event.result);
var ns:Namespace = new Namespace(doc.namespace());
default xml namespace = ns;
//some xml data extracting...
default xml namespace = new Namespace("");
}

Setting default xml namespace to the “”-namespace solved the problem!

That’s it!

In times of garbage collection you’re tempted to forget “tidying up” such things like the xml default namespace. But, honestly, it’s just a bug.

Look here:

http://soledadpenades.com/2007/07/03/verifyerror-error-1025-an-invalid-register-1-was-accessed/