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

Crash during shutdown #10

Closed
huebl opened this issue Sep 29, 2018 · 1 comment
Closed

Crash during shutdown #10

huebl opened this issue Sep 29, 2018 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@huebl
Copy link
Contributor

huebl commented Sep 29, 2018

When the application is shutdown (DiscoveryCient), access to the SlotTimerElement results in a CORE.

@huebl huebl added the bug Something isn't working label Sep 29, 2018
@huebl huebl self-assigned this Oct 17, 2018
@huebl
Copy link
Contributor Author

huebl commented Dec 26, 2018

The problem is fixed. But in the application there are many places where conflicts between multiple threads can occur. Therefore it is recommended to fundamentally revise the communication concept as well as the thread concept in a later release. See also #11.

Above all, the client session component is affected during the shutdown of the application.

@huebl huebl closed this as completed Dec 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant