#Pycharm http client how to

I attached a picture for a better understanding. I installed the version u mentioned and after a while I see my CPU usage stuck at 20% and never comes out and it is all because of IntelliJ after checking my task manager and performance monitoring section, I saw 3 threads are working near 100% (like 90%) and 2 more threads are working hard but they go up and down more frequently. no, it happens randomly, actually, I think it might not relate to the waking up the system the only thing that I am certain of right now is that it always happens after working with IntelliJ for a whileĪnd for the last part, since it is super annoying and makes my PC super slow I will appreciate any workaround and will install your version to test it, I’ll post the results.I have this problem with both Windows 10 and 11, my current windows 10 build is 4.1499 but I went through several updates until now.

#Pycharm http client how to

If you have time could you test this version where max 3 cores should be at 100% in case the bug happens ? You can find how to install it here.įor the first part, I didn’t quite understand what to do, I saw your repository do you want me to only run it in my system with JVM you mentioned, that’s all? Some cores would still be at 100% because of the bug though, so we can only reduce the effect of the bug, not make it disappear. We could provide some kind of workaround for that, like make sure we reduce the number of occupied cores. I will also try on my box.Ī couple more questions: what is the exact version of Windows you are using ? Does the issue happen only after waking up the PC, or also randomly when you are using it in normal conditions ? Could you give it a try on your side ? If you do, could you try with the JBR and a normal JDK ? Also make sure that SonarLint is not running at the same time. I extracted the client initialization section that I think is responsible of the issue into this small repository. Looks like the best thing to do is to write a small reproducer to narrow down the problem. I started a discussion on the Apache HTTP client mailing list.