We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The trace can contain several consecutive thread switches to the blocks of the same spin-loop.
Example:
| /* The following events repeat infinitely: */ | | ┌╶> state ➜ 0 at FutureTask.awaitDone(FutureTask.java:406) | | | LockSupport.park(FutureTask#1) at FutureTask.awaitDone(FutureTask.java:447) | | └╶╶ switch (reason: active lock detected) | | | | | | | | | | /* The following events repeat infinitely: */ | | ┌╶> state ➜ 0 at FutureTask.awaitDone(FutureTask.java:406) | | | LockSupport.park(FutureTask#1) at FutureTask.awaitDone(FutureTask.java:447) | | └╶╶ switch (reason: active lock detected) |
lincheck/src/jvm/test/resources/expected_logs/run_concurrent_test/thread_pool/thread_pool_jdk17.txt
Line 106 in f0b6b22
We need to fix this by merge several consecutive spin-loop blocks, and do not show redundant thread switches.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The trace can contain several consecutive thread switches to the blocks of the same spin-loop.
Example:
lincheck/src/jvm/test/resources/expected_logs/run_concurrent_test/thread_pool/thread_pool_jdk17.txt
Line 106 in f0b6b22
We need to fix this by merge several consecutive spin-loop blocks, and do not show redundant thread switches.
The text was updated successfully, but these errors were encountered: