-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Segmentation violation in Boost ASIO #3084
Comments
Other (asio) threads
Threads 20,21, and 22 have the same stack trace
Thread 23 is the one shown above Threads 24 through 35 have the same stack trace
Threads 36 through 39 have the same
|
try setting |
done, testing now. this takes from 1 to 5 days to occur so have 2 populations -- one with |
in fact, the network thread feature has been removed in master, and deliberately defaulted to 0 in 1.1.x, because it doesn't work. |
Haha, ok, well then as a followup, here are the results. After a week, I found that out of the population with network-threads set to a non zero value there were 5 crashes and in the population where it was set to 0, there were 0 crashes. |
Please provide the following information
libtorrent version (or branch):
libtorrent 1.1.4
boost 1.64
platform/architecture:
compiler and compiler version:
please describe what symptom you see, what you would expect to see instead and
how to reproduce it.
This is possibly out of the scope of libtorrent, but specific guards might be included to avoid it, or some warning how it may occur.
This seems likely to the known boost asio problem 7611
Here's the stack trace.
The text was updated successfully, but these errors were encountered: