Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashes at start when resuming/checking many torrents [RC5] #1682

Closed
colin1497 opened this issue Oct 14, 2015 · 2 comments
Closed

Crashes at start when resuming/checking many torrents [RC5] #1682

colin1497 opened this issue Oct 14, 2015 · 2 comments
Milestone

Comments

@colin1497
Copy link

Somewhere above 60 torrents seeding, anonymously, where all torrents are already downloaded, but because tribler is updating to a new version (6.5 from 6.4) it is checking each torrent at startup, tribler crashes with no log file while "building circuits."

Since I eventually got through this, I don't currently have a setup in the state to reproduce this bug, so it may be a little tough to check fixes.

Lots of information provided in #1605, splitting this issue out for tracking purposes.

This may actually be considered to be two bugs?

  1. The crash itself
  2. The lack of a log file
@colin1497 colin1497 changed the title Tribler Crashes at start when resuming/checking many torrents [RC5] Crashes at start when resuming/checking many torrents [RC5] Oct 14, 2015
@whirm whirm modified the milestones: Backlog, V6.5 Oct 16, 2015
@whirm
Copy link
Contributor

whirm commented Oct 16, 2015

If there's a segfault (as in the error doesn't happen in python space) it's expected that no log entries will be written. Not much to do about that except for installing a debugger so the process state can be inspected when it happens.

@whirm
Copy link
Contributor

whirm commented Oct 26, 2015

I've just tested a migration from 6.4.3 to 6.5RC5+ with 233 downloads (most of them in seeding state) and the upgrade went smoothly.

A bunch of bugs have been fixed since RC5, maybe you where hitting one of them?

I'll close this, but if somebody manages to get the same behavior with a >RC5 version, please reopen it.

@colin1497: I'll post RC6 shortly in case you are interested in further testing.

@whirm whirm closed this as completed Oct 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants