-
Notifications
You must be signed in to change notification settings - Fork 648
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
cli_tests memory access violation at address: no mapping at fault address #1303
Comments
are there any other related logs about stack execution ? more error logs will help very much. We have next code there:
My thoughts are that there is something wrong maybe in cli_fixture code or maybe some strange behavior with I believe the problem with
Thanks ! |
@ryanRfox assign this issue to me please and I will try to find the solution. My estimation is approximately 10 hours (because this issue not always reproduce-able and it is hard to catch it), if I will have some troubles and will need more time then I will notify you about that. Thanks ! |
I assigned @cogutvalera and added the estimation of 10 hours. May I request @abitmore to comment on the estimate? |
@ryanRfox IMHO better focus on more important things first. This is a minor issue so far. |
@abitmore and @ryanRfox Thank you very much ! Guys, I will do more important things first, and later will try to finish this issue, maybe soon at that time we can catch more error logs about this issue which will help to solve it. @abitmore and @ryanRfox can you help me please how to determine which issues are more important with highest priority ? Where can I see priorities from highest to lowest ? In project backlog only ? Thanks ! |
@cogutvalera in general I hope you will review the Project Backlog to identify |
@ryanRfox thank you very much for so detailed information ! |
https://travis-ci.org/bitshares/bitshares-core/builds/428368997
|
@abitmore Thanks for logs ! |
The program then hang. |
|
Fired in gdb, hang.
|
Fired in gdb again, crashed.
|
These logs may help a lot ! |
@ryanRfox this issue hasn't been fixed. |
|
It seems that here is a threading issue: https://github.com/bitshares/bitshares-fc/blob/b29da15d519d04651b07831f746f864fbac5190d/src/network/http/websocket.cpp#L265
Also there are similar code in the same function. I guess the situation is similar to #1256 . |
A normal run:
A crash:
Another crash:
Another crash:
Another crash:
Another crash:
|
For whatever reason, the lambda in The hang is something else, but perhaps related. |
I believe this has been fixed by #1626. By the way, cli_tests sometimes hang, we can open another issue for it. |
Bug Description
Sometimes (not always reproduce-able) when running
tests/cli_tests
, I got this message:Note: IIRC I've encountered it not only in
cli_quit
.Expected Behavior
No error.
Impacts
Host Environment
Please provide details about the host environment. Much of this information can be found running:
witness_node --version
.CORE TEAM TASK LIST
The text was updated successfully, but these errors were encountered: