If you really want to poke around in the binary, you can use a decompiler like IDA, Ghidra, or Binary Ninja's free version. Source: 8 months ago

Still $$$ for crippled functionality. As an alternative, https://binary.ninja is gaining traction at work. - Source: Hacker News / 11 months ago

As I said, a regular text editor won’t do for reading a binary file, so I needed to choose a disassembler to break the challenge binaries out into their basic blocks. I chose to use Binary Ninja because it has a very easy-to-use Python API, and it’s hobbyist-level cheap (for comparison, the industry-standard disassembler is IDA Pro, which they will sell to you for roughly an arm, and continue to pick off your... - Source: dev.to / over 3 years ago

It’s an awesome reverse engineering tool (https://binary.ninja). Has really nice api support so you can basically automate anything and make plugins for custom architectures and stuff like that. Source: almost 2 years ago

It's basically the opposite of https://godbolt.org/ -- put in binary, get out decompilation amongst many decompilers. It's open source (though you need a Binary Ninja and Hex-Rays license to run internally -- you'll want to check with the respective companies to make sure your particular license is acceptable for use even internally first!). Source: almost 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: about 1 year 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: about 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