That internal error stems from the symsym.pas procedure Tprocsym.deref in the compiler sources.
As far as I can see that can only happen if you mix interface references and class references to the same entity where either one of them has gone out of scope or free'd and it is referenced afterwards: the procdefdereflist is already destroyed but you are trying to use it. (It is always created!)
It should be reported, but we really need an example of how you use your interfaced code to see if the above is indeed the case and if the internal error is still thrown in fixes or trunk.
Note that the code path that throws the internal error also indicates that you made an error in the way you use interfaces. So even if the internal error does not occur, there is still your own error in the code, which may manifest itself as a warning or error, but also as e.g. a memory leak or a double free exception.