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

Operation deadlock at the application start. #62

Closed
PTKu opened this issue May 11, 2021 · 1 comment
Closed

Operation deadlock at the application start. #62

PTKu opened this issue May 11, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@PTKu
Copy link
Member

PTKu commented May 11, 2021

Describe the bug

At the start of the examples application and component's sandbox application sometimes the console stops at reading identities.

To Reproduce
Steps to reproduce the behavior:

  1. Run the application from https://github.com/TcOpenGroup/TcOpen/tree/initial-dev/src/TcoApplicationExamples/TcoApplicationExamples.Wpf
  2. 1 or > of 10 times the application will not start.

Expected behavior
The application starts every time.

Additional context
Seems the connector deadlocks due to the premature start of batch operations. If any batch operations are started after first cyclic R/W the behavior does not occur.

@PTKu PTKu added the bug Something isn't working label May 11, 2021
PTKu pushed a commit that referenced this issue May 13, 2021
@PTKu
Copy link
Member Author

PTKu commented Aug 9, 2021

Occurs when batch reading on the twin connector executes within UI dispatcher task. Batch R/W operation are not allowed on UI thread!

@PTKu PTKu closed this as completed Aug 9, 2021
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