Hi Team,
We in Energy Future holding are experiencing a memory leak issue. follwoing are the logs from the Dump.
13 Gb dump:
============
Managed, highest consumers:
0x000007ff00256988 366,908 300,144,240 System.Collections.Hashtable+bucket[]
0x000007ff000f96a8 4,592,087 315,011,440 System.Object[]
0x000007ff0026dc18 38,295 350,392,920 System.Byte[]
0x000007ff01234a70 25,087,194 802,790,208 Symantec.APM.I4DotNet.Collector.Structures.SingleLinkNode
0x00000000018530b0 4,374 1,462,181,928 Free
0x000007ff001e0d90 25,343,241 3,928,976,096 System.String
0x000007ff01265678 27,867,747 4,681,781,496 Symantec.APM.I4DotNet.Collector.Protocol.Event
Total 98,857,801 objects, Total size: 12,605,819,168
Choosing a random instance of Symantec's Collector.Protocol.Event class:
Structure of this Event object is as follows:
Name: Symantec.APM.I4DotNet.Collector.Protocol.Event
MethodTable: 000007ff01265678
EEClass: 000007ff0125b060
Size: 168(0xa8) bytes
MT Field Offset Type VT Attr Value Name
000007ff0039b448 4000023 98 System.Boolean 1 instance 1 isSent
000007ff012316c8 4000024 80 System.Int32 1 instance 0 eventType
000007ff00254408 4000025 58 System.Int64 1 instance 1385485993061 timestamp
000007ff00254408 4000026 60 System.Int64 1 instance 0 duration
000007ff00254408 4000027 68 System.Int64 1 instance 635210827931816918 eventTicks
000007ff01231818 4000028 84 System.Int32 1 instance 2 invocationType
000007ff0026cfc0 4000029 88 System.Int32 1 instance 16380 threadId
000007ff001e0d90 400002a 8 System.String 0 instance 1c00815f0 className
000007ff001e0d90 400002b 10 System.String 0 instance 181809ed0 methodName
000007ff001e0d90 400002c 18 System.String 0 instance 1c004e9f0 wsUrl
000007ff001e0d90 400002d 20 System.String 0 instance 181809ed0 httpUri
000007ff001e0d90 400002e 28 System.String 0 instance 1818065a0 httpMethod
000007ff002570f0 400002f 70 System.Double 1 instance 41.855068 cpuTime
000007ff002570f0 4000030 78 System.Double 1 instance 0.000000 tmpWorkTime
000007ff001e0d90 4000031 30 System.String 0 instance 1c004e9f0 sql
000007ff0039b448 4000032 99 System.Boolean 1 instance 0 hasSql
000007ff001e0d90 4000033 38 System.String 0 instance 1c004e9f0 database
000007ff001e0d90 4000034 40 System.String 0 instance 1c004e9f0 connString
000007ff0026cfc0 4000035 8c System.Int32 1 instance 0 queue
000007ff0026cfc0 4000036 90 System.Int32 1 instance 163800 uid
000007ff0026cfc0 4000037 94 System.Int32 1 instance 86415904 num
000007ff001e0d90 4000038 48 System.String 0 instance 181809f48 coloring
000007ff001e0d90 4000039 50 System.String 0 instance 0 destination
As can be seen, it has multiple strings and integers in it, which could/would explain why we have so many strings (and why number of strings grows).
These events appear to be related to some "tracker" (profiler??) that is Symantec's product:
Image path: C:\Windows\assembly\GAC_64\Tracker_x64\9.5.0.0__e5c85dd2303a5f34\Tracker_x64.dll
Image name: Tracker_x64.dll
Using CLR debugging support for all symbols
Has CLR image header, track-debug-data flag not set
Timestamp: Mon Apr 29 12:48:15 2013 (517EA44F)
CheckSum: 00049227
ImageSize: 00040000
File version: 9.5.0.0
Product version: 9.5.0.0
File flags: 0 (Mask 3F)
File OS: 4 Unknown Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0000.04b0
CompanyName: Precise Software Solutions, Inc. All Rights Reserved
ProductName: Precise Indepth for Microsoft .NET - version 9.5
InternalName: Tracker_x64.dll
OriginalFilename: Tracker_x64.dll
ProductVersion: 9.5.0.0
FileVersion: 9.5.0.0
FileDescription: Indepth for Microsoft .NET Tracker
LegalCopyright: Copyright © 2009 Precise Software Solutions, Inc
LegalTrademarks: i3™, Indepth™
Comments: Activity Data Collection Probe
Request you to please look into this .
and suggest what need to be done.
Env. SEP 12.1 RU3