Closed AlexJDowson closed 3 years ago
I've had similar stuff happen as well, it's pretty random but also consistent, in that it often will work, but if it doesn't work on a particular disc it will always fail on that disc.
I've had similar stuff happen as well, it's pretty random but also consistent, in that it often will work, but if it doesn't work on a particular disc it will always fail on that disc.
I'll try it with a couple more discs. Really sucks that this program is pratically unusable now, there's nothing that replaces it for me. It rips using cdparanoia, compresses into FLAC and organises all of the files. It does everything I need it to do.
That said, I have not tried it with another USB disc reader (I don't have one) so it could also be that (TSSTcorp BDDVDW SE-506AB TS01).
For what it might be worth to anybody, this is happening to me, as well. There is no indication of what is going on in the debug information, and the crashes don't occur after any particular debug line. They also occur on random tracks. I haven't tried another disc yet, but frankly, if it can't rip my whole collection, I will be exploring other options anyway. I will experiment a bit more over the next couple days.
Edit: I just ripped four discs two times each with no trouble through rubyripper_cli. Whatever this problem is, it appears to be GUI related.
Hi guys, sorry for the long delay concerning this issue. Yes, I'm also experiencing the same (I believe) crashes and I suspect they are related to scrolling of the log window during ripping. I have tried different approaches to fix this issue, currently without success. As a workaround, I have added a new option in preferences (in the 'Other' tab) to disable the auto log scrolling. If you ever have time, please try and report if this helps avoiding the problem. In the meantime, I'll will continue searching for the correct solution to this problem. Thanks!
I think this problem should be fixed with the port to GTK3. I'm closing this bug. Please, reopen it if the problem still exists on the master (GTK3) branch. It is still present on the stable branch (GTK2), but the workaround, see above comment, exists.
Using the latest version from git. Most of the time rubyripper crashes during ripping, sometimes it completes an entire CD this is rare. I'm using the GTK version on Arch Linux.
Running ./rubyripper_gtk2 from a terminal window gives me no useful output for debugging, just a crash with no output (seg fault?).
Enabling debug mode gives me this (I've anonymised the output):
It just checks the disk space and at the next step crashes without any explanation in the debug output.
Any ideas?