Objects stuck in purgatory

[pikzilla]

I have a small issue wherein a few bullet objects, which are specifically destroyed in the event editor once they reach a certain distance from the edges of the screen, do not seem to be fully deleted. What I mean by this is that I will still see the objects available in the debugger, but they cannot be added or examined accordingly. Clicking on their names in the `Add object to debugger` menu merely closes the menu and adds nothing. Due to this strange issue, my debugger will list over sixty different bullet objects as being in existence, even when there should be zero. There aren`t any direct gameplay implications of this strange issue, but as of late I have also been experiencing significant lag in certain bits, and feel the issues could be related. Can somebody explain to me what is going on?

[fawfulfan]

This has happened to me before too. I don't remember the exact circumstances (they were different than yours), but I've seen this bug in the past.

[pikzilla]

I have an interesting development, and what I believe to be a solution. It seems that for whatever reason the "inactive if too far from frame" option in the active objects` runtime properties was set to "automatic". For reasons I only vaguely grasp, setting the option to "off" allows me to destroy them entirely and upon my command. So that`s nice.