Symptoms
Assume that you enable the Resource Governor feature in an instance of Microsoft SQL Server 2016. When you execute a query that requests data from memory-optimized tables, regardless whether the query request is routed to the user-defined resource pools or the default resource pool, SQL Server may run out of memory and then freeze. Additionally, an error message that resembles the following is logged in the SQL Server error log:
Note
Error: 17300, Severity: 16, State: 1.SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option 'user connections' to check the maximum number of user connections allowed. Use sys.dm_exec_sessions to check the current number of sessions, including user processes.
Resolution
This issue is fixed in the following cumulative update for SQL Server:
Cumulative Update 1 for SQL Server 2016 SP1
Cumulative Update 4 for SQL Server 2016
About the 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:
Latest cumulative update for SQL Server 2016
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.