Proget with npm feed use massive a amounts of CPU/RAM

Hello.
I upgraded to Proget 3.6.1. to get rid of crashes in ProGet and now face other issues. Our npm feed is unusable since when the Npm is queried the ProGet service process starts to use enough memory to make the system very slow. My machine has 4GB of RAM and the process is allowed to consume about 3.2GB of it. This is a bug I assume?

Some things I have discovered

Reproducible in versions 3.5.5, 3.5.8 and 3.6.1
Before npm feed connector is indexed the peformance, the above behavior is not seen
While indexing I could see lots of indexing errors. I can't find that log now but I think it was complaining about not finding a 'versions'-tag

Let me know if I should add some logging or can help in any other way.

Niklas

Product: ProGet
Version: 3.6.1

When using an npm connector, the entire npm metabase must be downloaded from npmjs.org, and then indexed. This can take 5-15 minutes. After that, only incremental download/indexes occur.

I don't think this is the only thing happening here.

The proget service is holding on to every little ounce of memory in the machine (while not responding to requests) and doing so for, as far as I can tell, forever.

Is there something else we can do to troubleshoot? It's not usable at the moment for us.

Thanks for the answer,
Niklas

We have not had other users report this problem, nor have we seen it during testing.

You can try running the service interactively (just stop the WIndows Service, then run the .exe file), and see what happens.

Also worth noting, make sure that all the errors in the log are deleted before the packages start indexing again.