-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
5
-
2023-05-16 Chook-n-Nuts Farm
WT-10456 added the following assertion:
ASSERT(_icontext->_dyn_table_runtime[tint]._in_use > 0);
The field _in_use, when greater than 0, indicates that a thread is currently using that table. This prevents other threads from dropping the table for instance.
Where the assertion is, since a thread is done working on the table, we want to make sure the field is greater than 0 before decrementing it.
There are two things we should do to investigate:
- Why is this only done for operations on random tables?
- We should investigate where the field _in_use is incremented/decremented to make sure we have not forgotten anything.
EDIT: after investigating further, it seems that this comment explains the actual issue.