Killing processes while getting this information would be nice.
For more hardcore, there is also BleakHouse , which gives you a special compiled copy of ruby with better powarz memory leak tracking
A quick and dirty way will be ObjectSpace.each_object{|e| p e}. You can do some tests to determine what you wanted to keep, or marshal the objects.
ObjectSpace.each_object{|e| p e}
1.9.2/1.9.3 heap_dump gem, gdb ( , )
, , , .
Source: https://habr.com/ru/post/1697339/More articles:Silverlight XAP obfuscation - silverlightСинтаксис объявления JS-скриптов - javascriptGetting information about a physical device from a given file path - windowsCreate PDF from structured data - pdfWindows Server 2008 SSTP VPN in a non-domain environment? - sslInclude only specific libraries in the operating system - c ++File System Controls - sqlWhy am I getting the "wrong number of arguments (0 for 2)" exception in my Ruby code? - ruby | fooobar.comimplementation of a data access object template - c ++Очистить многокадровый веб-сайт - htmlAll Articles