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

Race condition related to the type cache initialization #1244

Open
PatrickKursawe opened this Issue Dec 7, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@PatrickKursawe

PatrickKursawe commented Dec 7, 2018

I get deadlocks in my project parallel test runs if I don't initialize the type cache before starting the tests. The issue is easy to reproduce for me, but unfortunately it is not an open source project. I'll try to strip it down and reproduce, but I'd like to already give you a heads up for the issue.

You find a stack trace of the problem in
https://stackoverflow.com/questions/53668571/catel-type-registration-hangs-in-parallel-unit-tests/53668930

Will try to build a test project showing this behavior.

@PatrickKursawe PatrickKursawe changed the title from Race condition in related to the type cache initialization to Race condition related to the type cache initialization Dec 7, 2018

@PatrickKursawe

This comment has been minimized.

PatrickKursawe commented Dec 10, 2018

Tried to find out the root problem, and of course, as soon as I start running the unit tests against a debug build of catel 5.8.0, the problem does not occur any more.

@GeertvanHorrik

This comment has been minimized.

Member

GeertvanHorrik commented Dec 10, 2018

Thanks for reporting. It might be a good hint that it does not happen in debug mode. We can still try to figure out the root cause and try to fix it :)

@GeertvanHorrik GeertvanHorrik self-assigned this Dec 10, 2018

@GeertvanHorrik GeertvanHorrik added this to the 5.9.0 milestone Dec 10, 2018

@GeertvanHorrik

This comment has been minimized.

Member

GeertvanHorrik commented Dec 10, 2018

I want to fix this for the next release, hopefully we can somehow create a repro and get this fixed (even if it's release-mode only, I am happy to have a repro).

@PatrickKursawe

This comment has been minimized.

PatrickKursawe commented Dec 10, 2018

Still failing (but still trying) to construct a test project that reproduces the error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment