Summary: | media-sound/rubyripper-0.5.7 stops working when used with dev-lang/ruby-1.8.7_p249 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Seerp <roaldkoudenburg> |
Component: | Current packages | Assignee: | Daniel Pielmeier <billie> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ruby, sound |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Seerp
2010-02-25 22:40:07 UTC
I can reproduce this issue, but here rubyripper is just slow. It seems to take very long for comparing the tracks (Analyzing files for mismatching chunks) and there is also a long pause after that and before converting the wav files to the chosen encoded format. Ruby is using some CPU during the slow phases though. This happens for both ruby-1.8.7_p249 and ruby-1.8.7_p299. A downgrade to ruby-1.8.6_p388 fixes the problem and ruby-1.8.7_p174-r1 should work too. There is also an upstream bug [1] about this issue where a comment says it is fixed in ruby-1.9. I can not test ruby-1.9.1_p429 as I experience bug #327051 and using -O0 or -O1 in CFLAGS does not fix the issue for me. @ruby-team: It would be nice if someone of you can comment on this issue. If there is nothing you can do about just remove yourself from CC. [1] http://code.google.com/p/rubyripper/issues/detail?id=348 This is most likely caused by changes in threading behaviour. Upstream is aware of those, but part of the incompatible changes where needed to fix other bugs. I guess the 1.9.1 version threading implementation is more robust and thus won't trigger this bug. I got the same problem, but i tried to rip using the cli and it works fine I just committed rubyripper-0.6.1 which fixes the issue for me. Please test! That's good news! Unfortunately I cannot test as I do not have a gentoo machine with optical drive anymore. I think it is okay to close this one for now. If anybody still has performance issues please reopen. |