FIX: Access violation occurs with wait_info XEvent on busy SQL Server

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

Symptoms


Consider thefollowing scenario:
  • You have an active session that collects the wait_info XEvent by using global actions such as sql_text or plan_handle. The wait_info XEvent is also collected by the default system_health session.
  • The system is busy running many concurrent serial and parallel queries.
In thisscenario, if there's a delay in shutting down a parallel request, a wait_infoXEvent may be triggered. When the parallel request is shut down beforethe XEvent global action is completed, an access violation may occur.

Status


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

Resolution


This issue is fixed in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

References


Learn about the terminology that Microsoft uses to describe software updates.