FIX: SQL Server 2016 stops responding when the "Latch_Suspend_End" extended event is incorrectly triggered

Applies to: SQL Server 2016 Enterprise CoreSQL Server 2016 EnterpriseSQL Server 2016 Developer


Assume that you configure an Extended Event session that monitors the Latch_Suspend_End event in Microsoft SQL Server 2016. When a worker thread is aborted or receives an abort attention, the Latch_Suspend_End event is incorrectly triggered while a latch is obtained successfully. This causes a latch leakage assertion. Additionally, SQL Server stops responding.


The fix for this problem is included in the following updates:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology Microsoft uses to describe software updates.