WinDbg VS VisualVM

Windows 11, version 22H2 release of the WDK Installed + added to Visual Studio. Source: 10 months ago

The stack frames will look cryptic, but if that's good enough for you -- there you go! If you want a clearer ST, you'll have to download and install Debug Tools and load Debug Symbols into the ProcessExplorer as shown in tutorials:. - Source: dev.to / over 1 year ago

Okay, here’s an SDK I use. It’s 16GB. https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk#enterprise-wdk-ewdk Show me how to use this with GitHub actions, if it’s not too hard. - Source: Hacker News / about 2 years ago

1) I have downloaded VScode, windows SDK, windows WDK, and the EWDK. The video only mentions downloading the first three items ^. However, the windows link I used to download the SDK and WDK had a 3rd step to download the EWDK. Link for Reference. What is an EWDK and do I need it? 2) I am using windows and the video says to download a VM. I assume I do not need to do that because I am already in windows. If my... Source: over 2 years ago

I also downloaded the " Windows Driver Kit (WDK). " Not really sure what to do next... Source: over 2 years ago

If you're curious, attach VisualVM and watch the RAM usage graph. You'll notice that Java performs garbage collections long before reaching allocating the maximum amount of RAM allocated, and you can't even feel any performance issue in-game. Source: 12 months ago

Hangs and deadlocks are significantly harder to debug. A first step is taking a thread dump so you can see what each thread in the JVM is currently trying to do. I like VisualVM for this, you can also use the command-line tools jps -l (to list all Java PIDs) and jstack for taking a thread dump. Source: almost 1 year ago

The Java VisualVM project is an advanced dashboard for Memory and CPU monitoring. It features advanced resource visualization, as well as process and thread utilization. - Source: dev.to / about 1 year ago

This sounds like a server thread freeze/deadlock/crash or something. I think I would start debugging this using a tool like VisualVM; attach it to the game, wait for the hang, take a thread dump, and check what the server thread is up to. Source: about 1 year ago

Just wanted to chip in to say that /u/UtilFunction is correct. The proper way to measure memory consumption of any Java application independent of which garbage collector is used is to perform a heap dump (which automatically forces a complete garbage collection). I like to use VisualVM for that. Source: about 1 year ago