Open GoogleCodeExporter opened 8 years ago
Just saw this as well with current git:
/software/rubyripper/lib/rubyripper/secureRip.rb:330:in `block (2 levels) in
correctErrorPos': Wrong class for errors[key]: NilClass (RuntimeError)
from /software/rubyripper/lib/rubyripper/secureRip.rb:328:in `each'
from /software/rubyripper/lib/rubyripper/secureRip.rb:328:in `block in correctErrorPos'
from /software/rubyripper/lib/rubyripper/secureRip.rb:325:in `each'
from /software/rubyripper/lib/rubyripper/secureRip.rb:325:in `correctErrorPos'
from /software/rubyripper/lib/rubyripper/secureRip.rb:162:in `main'
from /software/rubyripper/lib/rubyripper/secureRip.rb:98:in `ripTrack'
from /software/rubyripper/lib/rubyripper/secureRip.rb:75:in `block in ripTracks'
from /software/rubyripper/lib/rubyripper/secureRip.rb:71:in `each'
from /software/rubyripper/lib/rubyripper/secureRip.rb:71:in `ripTracks'
from /software/rubyripper/lib/rubyripper/secureRip.rb:60:in `startTheRip'
from /software/rubyripper/lib/rubyripper/rubyripper.rb:63:in `startRip'
from /software/rubyripper/bin/rubyripper_gtk2:385:in `block in updateInterfaceAndStartRip'
Original comment by hanno@hboeck.de
on 25 Dec 2012 at 4:17
Original comment by boukewou...@gmail.com
on 9 Jan 2013 at 10:51
Which version of Ruby are you using? I can't find anything wrong in the code
here. I did move the line in question since this saves some CPU cycles. Perhaps
this helps?
Can you reproduce? If so, what are your ripping settings?
Original comment by boukewou...@gmail.com
on 24 Jan 2013 at 8:35
ruby 1.9.3p286
It was never really reliably reproducible, but I'll do some tests to see.
Original comment by hanno@hboeck.de
on 24 Jan 2013 at 8:42
I did find something after all that just might explain the strange behaviour.
Please retry. See also commit:
http://code.google.com/p/rubyripper/source/detail?r=d74cbef1641ac617fc13bb16673e
dcdb31a9d806
Original comment by boukewou...@gmail.com
on 24 Jan 2013 at 8:47
You have more chances to trigger this code if you use a heavily scratched disc
:P. This code is only triggered when correction is needed.
Original comment by boukewou...@gmail.com
on 24 Jan 2013 at 8:54
Original issue reported on code.google.com by
pm.deb...@googlemail.com
on 8 Jun 2012 at 8:06