No matter how much memory I have, the load dies at around 93%. Here is the log from the last time I tried it, starting Yourkit with a 96G heap!
It ends with exception caught at ObjectStorageNatives.cpp:369
The error happens during the most memory hungry operation - the dominator tree calculation. As a workaround you can skip it by adding the following line to the file <profiler installation directory>/bin/yjp.ini:
-Dyjp.dominators=false
This should allow the snapshot to load, but retained sizes will not be immediately shown for individual objects in object explorers; instead, retained size will be shown equal to the shallow size. Also, the Biggest objects/dominator tree view will be incorrect - it will also be build on shallow sizes. But it's not a big problem: you can explicitly calculate retained size for a selected item by using Quick info (Ctrl+Q). Class list will show retained sizes after applying Calculate exact retained sizes.
I tried 8g heap and it died the same way. (Error box says "Not enough virtual memory" btw).
I tried 4g heap and it dies with java.lang.OutOfMemoryError: Java heap space.
I will try your -Dyjp.dominators=false suggestion with 8g heap next (also downloaded 12.0.1).
One thing is making it very difficult to use the tool with the -Dyjp.dominators=false setting.
I am tracking down instances to see where our memory is being used and I do a quick info to get the real retained size on various elements but the table doesn't update with this real value.
Any ideas on how to work around this?
Which table do you mean? If it's the Class list view or another view having "Calculate exact retained sizes" control - use it. Otherwise you can't have the exact sizes without using Quick info.
Note: -Dyjp.dominators=false is not a normal mode of operation. It's just a workaround to enable loading of huge snapshots on machines with lack of memory.
So I can only suggest to find a 64-bit machine with more memory available and try opening the snapshot on it.