Once a project has a dependency tree with a cycle in it (e.g., a -> a), visiting the all changes link will loop infinitely, using up memory and resources as it does. It would be nice if it detected that situation and avoided it, perhaps even presenting an error.

I have not yet determined why some of my builds have circular dependencies.