You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Server crash or freeze are possible as after-effects, and possibly index corruptions as well. It's reproducible easier with v2.5 than with v2.1.
This issue is caused by some logic errors in synchronization related to the monitoring activities. It may occur under quite rare condition when the lock requester gets its AST delivered while it's still waiting inside the lock manager (lock is granted but the thread still cannot check-in back into the engine) and it happens twice subsequently.
Submitted by: @dyemanov
Is duplicated by CORE2630
Attachments:
core-2993.src.7z
core-2993.exe.7z
Server crash or freeze are possible as after-effects, and possibly index corruptions as well. It's reproducible easier with v2.5 than with v2.1.
This issue is caused by some logic errors in synchronization related to the monitoring activities. It may occur under quite rare condition when the lock requester gets its AST delivered while it's still waiting inside the lock manager (lock is granted but the thread still cannot check-in back into the engine) and it happens twice subsequently.
Commits: e8a75e9 1674db2 7acd5e6 870cc30 7d94997 75080a1
The text was updated successfully, but these errors were encountered: