This looks like a bug in the debugger I actually ran into myself earlier this week. And I fixed it in the NextGen environment. That bug is pretty old, and I thought I had just bad luck running into it, but now I realize that the embedding of the manifest file likely exposed this (didn't realize that earlier this week). It depends on the size of the symbol table, so adding/removing/renaming a procedure/property/object influences it.