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

google_pipeline_tests falls in deadlock #3

Open
admo opened this issue Oct 26, 2016 · 2 comments
Open

google_pipeline_tests falls in deadlock #3

admo opened this issue Oct 26, 2016 · 2 comments

Comments

@admo
Copy link

admo commented Oct 26, 2016

Hi,
I would like to use your library in my project. Unfortunately I've (probably) found a bug.
I've compiled google_pipeline_tests, and run it in a loop. In most cases it ends as expected, but sometimes it hangs. The output is as following:
Running 3 test cases...
get for 2
get for 4
get for 6
get for 8
get for 10
Consuming user (User : 2)
Consuming user (User : 4)
Consuming user (User : 6)
Consuming user (User : 8)
Consuming user (User : 10)
find_uid for Foo
find_uid for BarA
find_uid for BazBB
find_uid for QuxCCC
get for 3
get for 3
get for 4
get for 4
get for 5
get for 5
get for 6
get for 6
Consuming user (User : 3)
Consuming user (User : 3)
Consuming user (User : 4)
Consuming user (User : 4)
Consuming user (User : 5)
Consuming user (User : 5)
Consuming user (User : 6)
Consuming user (User : 6)

Sometimes it prints out also:
a.out: /usr/include/boost/thread/pthread/condition_variable_fwd.hpp:81: boost::condition_variable::~condition_variable(): Assertion `!ret' failed.
unknown location(0): fatal error in "Example": signal: SIGABRT (application abort requested)

I've built this test with boost 1.58 on ubuntu 16.04.1 with gcc 5.4.0.
Have you faced such problem?
If you want I can provide more information, e.g. backtraces.

@erenon
Copy link
Owner

erenon commented Oct 26, 2016

Hi,
Sorry, I have no free time to support this library.

It might be worthwhile to raise this issue on the boost mailing list if

  • it is reproducible using the latest boost version, and
  • it is a result of correct usage of a condvar.

Thanks,
Benedek

On Oct 26, 2016 12:09, "Adam Oleksy" [email protected] wrote:

Hi,
I would like to use your library in my project. Unfortunately I've
(probably) found a bug.
I've compiled google_pipeline_tests, and run it in a loop. In most cases it
ends as expected, but sometimes it hangs. The output is as following:
Running 3 test cases...
get for 2
get for 4
get for 6
get for 8
get for 10
Consuming user (User : 2)
Consuming user (User : 4)
Consuming user (User : 6)
Consuming user (User : 8)
Consuming user (User : 10)
find_uid for Foo
find_uid for BarA
find_uid for BazBB
find_uid for QuxCCC
get for 3
get for 3
get for 4
get for 4
get for 5
get for 5
get for 6
get for 6
Consuming user (User : 3)
Consuming user (User : 3)
Consuming user (User : 4)
Consuming user (User : 4)
Consuming user (User : 5)
Consuming user (User : 5)
Consuming user (User : 6)
Consuming user (User : 6)

Sometimes it prints out also:
a.out: /usr/include/boost/thread/pthread/condition_variable_fwd.hpp:81:
boost::condition_variable::~condition_variable(): Assertion `!ret' failed.
unknown location(0): fatal error in "Example": signal: SIGABRT (application
abort requested)

I've built this test with boost 1.58 on ubuntu 16.04.1 with gcc 5.4.0.
Have you faced such problem?
If you want I can provide more information, e.g. backtraces.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3, or mute the thread
https://github.com/notifications/unsubscribe-auth/AALsM2dhXbkk5UaRqCwHpDw_KLCulwKcks5q3ybNgaJpZM4Kg_QJ
.

@admo
Copy link
Author

admo commented Oct 26, 2016

Hi Benedek,
Thank you for response. I understand that this project is not under the development.
I will do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants