gem runs endless loop

Bug #1662223 reported by Hadmut Danisch
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ruby-defaults (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Hi,

a simple gem command just jumped into a an endless loop with 100% CPU usage (while installing ri):

% sudo gem install sinatra
[sudo] Passwort für danisch:
Fetching: sinatra-1.4.8.gem (100%)
Successfully installed sinatra-1.4.8
Parsing documentation for sinatra-1.4.8
Installing ri documentation for sinatra-1.4.8

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ruby 1:2.3.0+4
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Feb 6 17:08:58 2017
InstallationDate: Installed on 2016-04-22 (290 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: ruby-defaults
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (112 days ago)

Revision history for this message
Hadmut Danisch (hadmut) wrote :
Revision history for this message
Hadmut Danisch (hadmut) wrote :

gem install --no-ri works..

Revision history for this message
Joshua Powers (powersj) wrote :

How long did you let it run for? Is this a small system? I tried this in a container and found that it did indeed cause my CPU to run up to 100% for a minute or so, but then completed:

Parsing documentation for sinatra-1.4.8
Installing ri documentation for sinatra-1.4.8
Done installing documentation for rack, tilt, rack-protection, sinatra after 28 seconds
4 gems installed

It appears that parsing the documentation causes significant CPU usage. I am going to mark this as incomplete rather than confirmed since I was able to complete the install.

Changed in ruby-defaults (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Joshua Powers (powersj) wrote :

Well obviously it wasn't a minute, since it says "after 28 seconds", but you get the idea :) It sat for a bit.

Revision history for this message
Hadmut Danisch (hadmut) wrote :

> How long did you let it run for?

Precisely as long as it took me to go to the kitchen and prepare some meal for dinner. Didn't check the time.

System is a Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz

Revision history for this message
Joshua Powers (powersj) wrote :

Rather than using the version via gem, have you considered using the version in Ubuntu via 'apt install ruby-sinatra' and see if that gets around your issue when using gem?

Given the is the bug tracker for Ubuntu we are not the best source of help to resolve an issue via gem, pip, etc.

Revision history for this message
Hadmut Danisch (hadmut) wrote :

Yeah, but the Ubuntu-Version was not running with other gems correctly, is outdated. That's why I had to throw it away and use the gem version.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ruby-defaults (Ubuntu) because there has been no activity for 60 days.]

Changed in ruby-defaults (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.