That makes sense to me.

My Track objects have no constituent Point objects. ``DummyTrack`` confers its track id number to each ``Point`` assigned to it, but it does not remember the Point, so Points release the references on each iteration of the loop. Thus, I am pretty sure the memory footprint is fixed and modest. My old limit was about 2000 frames before I raised a ``MemoryError``; now I'm running 20,000 with no problem.

Since you like this use case, I can try pulling more of my wrapping code into trackpy proper. The result will probably be much better. What I've done here is a somewhat kludgy because I wanted to edit as few lines of trackpy as possible.

Worth a try?