Assume that you create an XEvent session that has predicates in Microsoft SQL Server 2012. When you start and stop the XEvent session repeatedly, memory leak occurs and you notice that the memory allocated by 'MEMORYCLERK_XE' increases gradually.
Here is a sample XEvent session that demonstrates the behavior:

ADD EVENT sqlserver.module_end(
ACTION (sqlserver.client_app_name,sqlserver.plan_handle,sqlserver.session_id,sqlserver.sql_text)
WHERE ([package0].[Greater_than_equal_unicode_string]([sqlserver].[client_app_name],'MyApplication1')

Note You can monitor this memory leak by using the following query or by executing DBCC MEMORYSTATUS:

select [Memory Used KB] = page_size_in_bytes /1024  from sys.dm_os_memory_clerks where type = 'MEMORYCLERK_XE'

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:


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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!