@ara1
I cannot comment specifically on version 6.29 since I have not yet tried it.
But in the past, I have seen something similar using the watchlists: in my case, the list included some "old" symbols that were previously deleted from the DB.
Normally, when working with AmiBroker, when you delete a symbol from the DB in the correct way, it is also removed from any watchlist, but sometimes, probably due to some strange circumstance or a system malfunction, a watchlist file may not be updated correctly (no purging of the deleted symbols).
When AmiBroker starts, it loads the watchlists associated to a DB from the "watchlists" folder that is a child of the main DB folder.
In this watchlists folder, there are multiple files, and each one is corresponding to a watchlist.
Using a text editor open the file of the watchlist where you saw the "extra" symbols.
Are they in this file too? If not, ignore the rest of this post.
Otherwise, it is not a debugView issue. Simply close all the instances of AmiBroker and edit the file removing the unwanted symbols and save it again.
Reopen AmiBroker and do your test again. This should fix the anomaly.
Normally, when working with AmiBroker, when you delete a symbol from the DB in the correct way, it is also removed from any watchlist, but sometimes, probably due to some strange circumstance or system malfunctions, a watchlist file may not be updated correctly (no purging of the deleted symbols).
The issue is a subtle one, since AmiBroker, at startup, checks the watchlists content and removes from the displayed lists any "extra" symbol that is no longer in the database (so you do not see them in the UI).
This means that it is possible to discover this rare anomaly only when using a function like CategoryGetSymbols() that seems to access the stored file instead of the in-memory list (I actually found this when I was using it for some ranking purposes and had some "foreign" empty arrays due to non-existent symbols).
Editing the misaligned watchlist file outside of AmiBroker seems to be the quickest way to fix the issue.