You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to produce a heap dump from a Rails console but there seems to be a problem with the message queue. I put rbtrace in my Gemfile with require:false, then I started the Rails console (bundle exec rails c), then I ran "require 'rbtrace'" in the console and got "true" as a response.
In another window I looked up the PID of the ruby process and ran:
rbtrace --pid 6591 --gc
Which gave me:
Error: argument --pid (pid is not listening for messages, did you require "rbtrace").
I looked in /tmp and there were indeed no rbtrace socket files that I could see.
I am running Ubuntu 14.04, Rails 3.2.21, Ruby 2.1.4p265 - if any of that matters.
Any ideas?
The text was updated successfully, but these errors were encountered:
Attaching to an irb console won't work because the console is generally "stuck" waiting for input on the prompt, so it is unable to respond to the requests coming from the rbtrace process.
Hi!
I am trying to produce a heap dump from a Rails console but there seems to be a problem with the message queue. I put rbtrace in my Gemfile with require:false, then I started the Rails console (bundle exec rails c), then I ran "require 'rbtrace'" in the console and got "true" as a response.
In another window I looked up the PID of the ruby process and ran:
rbtrace --pid 6591 --gc
Which gave me:
Error: argument --pid (pid is not listening for messages, did you
require "rbtrace"
).I looked in /tmp and there were indeed no rbtrace socket files that I could see.
I am running Ubuntu 14.04, Rails 3.2.21, Ruby 2.1.4p265 - if any of that matters.
Any ideas?
The text was updated successfully, but these errors were encountered: