Ruby Interactive Console Performance w/Nokogiri objects versus RubyMine

Answered

When debugging a JRuby application, if larger Nokogiri object exists, command evaluation is dreadfully slow.

With identical settings in Rubymine, this behaviour cannot be reproduced.

This is on Mac OS 10.13.6, with JRE 1.8.0_152.

IntelliJ IDEA is at 2018.3.3 w/Ruby v2018.3.20190109.

Rubymine is at 2018.2.5.

I'm using JRuby 9.2.0.0 and Nokogiri 1.10.1 through rvm.

 

I'm at a bit of a loss here because in order to reproduce the issue I must use IDEA and parse a webpage with a larger table on it, such as https://www.ncaa.com/rankings/basketball-men/d1/ncaa-mens-basketball-net-rankings as well as having the variable definition in the editor.  Toggling inline values display does not change the behaviour.  The issue cannot be reproduced in RubyMine.

Any ideas?

6 comments
Comment actions Permalink

Gah! I have his issue too. I wish it would just avoid showing the contents for large objects (like Nokogiri::HTML). Whenever my debugger his these areas of my code I have to force quit :(

0
Comment actions Permalink

Hello,

would it be possible to check how it goes in IDEA 2019.1 Beta2 with the updated Ruby plugin?

0
Comment actions Permalink

I have this exact problem.  Has anyone found a solution?

0
Comment actions Permalink

@Ian, have you tried the latest IDE 2019.2 version with the updated debugger gems?

0
Comment actions Permalink

I was using the latest version and per your suggestion I just tried updating to 2019.2 EAP with Java 11.  This made the IDE download a new debugger gem which I assume is the latest.  The problem still occurs.  When Nokogir parses the html response of a page the entire IDE locks up and you have to force quit.  Just for testing I did this with the source of an amazon page but I've also tested it with other html source.  I'm able to get around this by using pry insead of the RubyMine debugger but this is obviously not ideal.  Any help would be greatly appreciated!

0
Comment actions Permalink

We have an issue with performance degradation while debugging Nokogiri so probably it's related: https://youtrack.jetbrains.com/issue/RUBY-24258

0

Please sign in to leave a comment.