"Collecting Data" always shows up in RubyMine debugger Variable pane

Completed

I have the following issue when I use RubyMine to debug rails code:

1. I setup the break poing in a rails code, and run the debugger.

2. when that break point is hit, I open the variable pane.

3. When I click one of the variable to check its value, I always get Collecting Data....

 

I am running RubyMIne RubyMine 2016.2 (Build #RM-162.1236.17, built on July 19, 2016) and Jruby (9.0.5.0)  The OS is OS X El Capitan

 

 

0
8 comments

Hi Olga,


I finally figured it out. The issue was caused by one of ruby environment variables was turned off. Once it is turned on, RM debug works great!  Thanks a lot for offering the help. 

 

Sean

 

1

Hello, Sean,

could you please attach the output of gem list for your jruby SDK.

0

Hi Olga,

The following is the local gem list. Thanks.

 

Sean

-------------------------------------------------------------------------------------------


*** LOCAL GEMS ***

actionmailer (4.2.6)
actionpack (4.2.6)
actionview (4.2.6)
activejob (4.2.6)
activemodel (4.2.6)
activerecord (4.2.6)
activesupport (4.2.6)
akami (1.3.1)
arel (6.0.3)
bcrypt (3.1.11 java, 3.1.10 java)
better_errors (2.1.1)
builder (3.2.2)
bundler (1.12.5)
bundler-unload (1.0.2)
chosen-rails (1.5.2)
coderay (1.1.1)
coffee-rails (4.1.1)
coffee-script (2.4.1)
coffee-script-source (1.10.0)
concurrent-ruby (1.0.2 java, 1.0.1 java)
dalli (2.7.6)
diff-lcs (1.2.5)
domain_name (0.5.20160615, 0.5.20160310)
erubis (2.7.0)
execjs (2.7.0, 2.6.0)
executable-hooks (1.3.2)
ffi (1.9.14 java, 1.9.10 java)
font-awesome-sass (4.5.0)
gem-wrappers (1.2.7)
globalid (0.3.7, 0.3.6)
gyoku (1.3.1)
highcharts-rails (4.1.10, 4.1.9)
http-cookie (1.0.2)
httpi (2.4.2, 2.4.1)
i18n (0.7.0)
jar-dependencies (0.2.3)
jbuilder (2.6.0, 2.4.1)
jquery-cropper (2.3.2, 2.2.5)
jquery-datatables-rails (3.3.0)
jquery-rails (4.1.1)
jquery-ui-rails (5.0.5)
jquery_autocomplete_rails (1.2.9.2)
jruby-jars (9.1.2.0, 9.0.5.0)
jruby-launcher (1.1.1 java)
jruby-openssl (0.9.17 java, 0.9.15 java)
jruby-rack (1.1.20)
jruby-rack-worker (0.11.0, 0.10.1)
json (1.8.3 java, 1.8.0 java)
loofah (2.0.3)
mail (2.6.4)
maskedinput-rails (1.4.0.0)
method_source (0.8.2)
mime-types (2.99.2, 2.99.1)
mini_portile (0.5.3)
minitest (5.9.0, 5.8.4, 5.4.1)
multi_json (1.12.1, 1.11.2)
netrc (0.11.0)
nokogiri (1.6.1 java)
nori (2.6.0)
power_assert (0.2.3)
pry (0.10.4 java, 0.10.3 java)
psych (2.0.15 java)
puma (3.6.0 java, 3.2.0 java)
racc (1.4.13 java)
rack (1.6.4)
rack-test (0.6.3)
rails (4.2.6)
rails-deprecated_sanitizer (1.0.3)
rails-dom-testing (1.0.7)
rails-html-sanitizer (1.0.3)
railties (4.2.6)
rake (11.2.2, 10.1.0)
rdoc (4.2.2, 4.1.2)
responders (2.2.0, 2.1.2)
rest-client (1.8.0)
rspec-core (3.5.2, 3.4.4)
rspec-expectations (3.5.0, 3.4.0)
rspec-mocks (3.5.0, 3.4.1)
rspec-rails (3.5.1, 3.4.2)
rspec-support (3.5.0, 3.4.1)
ruby-debug-base (0.10.6 java)
ruby-debug-ide (0.6.1.beta2)
rubygems-bundler (1.4.4)
rubyzip (1.1.7)
rvm (1.11.3.9)
sass (3.4.22)
sass-rails (5.0.6, 5.0.4)
savon (2.11.1)
sdoc (0.4.1)
slop (3.6.0)
socksify (1.7.0)
spoon (0.0.4)
sprockets (3.7.0, 3.5.2)
sprockets-rails (3.1.1, 3.0.4)
test-unit (3.0.3)
therubyrhino (2.0.4)
therubyrhino_jar (1.7.6)
thor (0.19.1)
thread_safe (0.3.5 java)
tilt (2.0.5, 2.0.2)
tzinfo (1.2.2)
tzinfo-data (1.2016.6, 1.2016.3)
uglifier (3.0.1, 3.0.0)
unf (0.1.4 java)
warbler (2.0.0.rc1)
wasabi (3.5.0)

0

Sean,

does it happen only within this specific project? Would it be possible for you to share it with me (you can write me to rubymine-support@jetbrains.com)

0

Hi,

I met this issue as well. 

Can anyone tell me how to fix or workaround it?

 

BR

Holt

0

Hello Holt,

could you please specify your RubyMine and Ruby versions? What is the exact error message?

0

Hi Olga,

My rubymine version: 2019.3

Ruby version: ruby 2.4.3p205 (2017-12-14 revision 61247) [x64-mingw32].

 

It is actually not an error, I just cannot see them debug intermediate data, shows "Collecting data...", like

 

0

Hello Holt,

sorry for such a delay. Would it be possible to test the latest RubyMine version (2020.1.2 RC) with the updated debug gems? Does the issue persist there? If yes, then it'd be great if you could provide a project/code sample for reproduce.

0

Please sign in to leave a comment.