As part of Module.linkInitial execution, Module.setDependencies visits all the current modules' dependencies to determine the current Module's paths.
The same method is later invoked for every dependency (as part of the same linkInitial execution) , in order to determine the current Module's dependencies paths. The result is that the same dependency is visited more than once.
To avoid that, the first execution of Module.setDependencies should store the path result for the dependencies, besides doing so for the current Module.