This post originated from an RSS feed registered with Ruby Buzz
by Max Zone.
Original Post: Inspecting a live Ruby process
Feed Title: dzone.com: ruby
Feed URL: http://feeds.dzone.com/dzone/ruby
Feed Description: dzone.com: fresh ruby and rails links for developers
So, there are you. Logged into one of your production machines, staring at a rogue Ruby process, and wondering why it has been running away with 90% of the CPU for the last half hour. Sure, you can kill it, but you���d really like to know why it is stuck there. This isn���t the first time you���ve noticed this problem, and you���re getting a little tired of manually patching things up. But how do you figure out where the process is stuck?
Previous Topic
