ClassPath detection incomplete/non-deterministic when using parallel scans

On version 4.8.138

If I construct a ClassGraph instance and have it scan the current classloader, eg:

new ClassGraph()
  .addClassLoader(classLoader)
  .scan()
  .getClasspathFiles()

The results change each time I run it and are generally incomplete (missing many entries). For example, I frequently will only get <50 entries back from a classpath of 800+ items.

If I simply change scan() to scan(1), the results are correct and deterministic. I do have logs for the incorrect and correct runs, but need to work on trying to sanitize them before I upload them here.

I suspect the problem might be that the root/only direct classpath entry is a classpath manifest jar. That then expands to a large (800+) jar classpath.

Any ideas what might be going on here?

[steveniemitz]

oh no worries/rush! I just wanted to make sure it had gotten to you. On my end I’ve worked around the bug so its not blocking anything for me, take your time!

[lukehutch]

Sorry, actually this is fixed in 4.8.145 (4.8.144 broke Windows compatibility).