This is a known issue that happens with unnamed procs--specifically, it's very common with cases where an object is initialized. If you setup a mob like this for example:


That would initialize a list with a nameless proc. (In this example it's also a bad idea, since mob/var/list/party will allow you to init the list only when needed.)

I believe there's a bug report or feature request already open for this.