Yourkit windows 7

By browsing our website, you consent to our use of cookies and other tracking technologies in accordance with the Privacy Policy. Java Profiler. NET Profiler. Easy to use performance and memory. NET profiler for Windows and Linux. You Monitor. Extremly slow by nemusns » Wed Dec 09, am YourKit 8.

I am not talking about using Yourkit during profiling, it is that slow even when there is no profiling at all. I can not even click on menus. What could be the problem? This really kills my productivity. What is particular slow task? Community Bot 1 1 1 silver badge. Niel de Wet Niel de Wet 6, 7 7 gold badges 52 52 silver badges 93 93 bronze badges. Add a comment. Active Oldest Votes. Vladimir Kondratyev Vladimir Kondratyev 5 5 silver badges 6 6 bronze badges. You are quite right, I was mistakenly assuming that the JRE installed on my Windows7 machine would be 64 bit.

In fact it was 32 bit. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.

Email Required, but never shown. The Overflow Blog. Invoking System. Asked 3 years, 3 months ago. Active 3 years, 3 months ago. Viewed times. Why is this happening? From what I can see, the heap behaves as expected, i. Yes, my question is why the 'allocated all pools' is growing continuously.

So, did you try with a different monitoring tool e. VisualVM or FlightRecorder and compare the result? Looking with ProcessExplorer shows the private bytes growing at the same rate as 'allocated all pools'.

The process continues to allocate more memory, presumably for the GC, and I'd like to know why it's allocating so much — beirtipol.

Also, trying with other tools helps verifying that the memory allocation is not caused by YourKit itself. Add a comment. Active Oldest Votes. In short, not all objects can be cleaned up in one cycle. Vinnie Vinnie 4 4 silver badges 19 19 bronze badges. What if the heap itself gets filled up and there is a need for Full GC.

What space does GC thread use in that case, reserved space? That makes sense for the first call, but does it keep duplicating the queue of references for cleanup?