Skip to main content

Timeline for ECL Connector Memory Leak

Current License: CC BY-SA 3.0

11 events
when toggle format what by license comment
Jun 17, 2020 at 9:55 history edited CommunityBot
Commonmark migration
Jul 5, 2017 at 15:08 vote accept Andy Ross
Jun 26, 2017 at 8:38 comment added Alvin Reyes Having taken a look with Andrew on this, we're also seeing that stopping IIS as well as services on the Content Manager (batch processor, publishing/transport, and search, which probably isn't related) does not free up CPU or memory. Interestingly, running a trace file also won't generate an actual file (meaning nothing is outputing trace details?). Officially we'll continue on this with Support and the creator of the ECL connector, but we can add details and hopefully a resolution soon.
Jun 24, 2017 at 22:20 history tweeted twitter.com/StackTridion/status/878739674088574979
Jun 23, 2017 at 11:46 comment added Atila Sos We have an open task to investigate potential memory leakage on our environment (Tridion 2013SP1), but haven't gotten around to it yet. We also have a similar behavior in a sense that the TcmServiceHost.exe 's memory usage is increasing over time. As mentioned earlier, I haven't gotten around to it, so I can't confirm or disregard your suspicions about ECL being the culprit. We are using SDL MediaManager, but also have lots of other customization like Event Systems etc.
Jun 23, 2017 at 11:45 history edited Andy Ross
edited tags
Jun 23, 2017 at 11:45 comment added Andy Ross I removed MM tag.. I just thought I needed that kind of audience. But it's a custom ECL provider..
Jun 23, 2017 at 10:03 answer added Lars Møllebjerg timeline score: 7
Jun 23, 2017 at 7:14 comment added Bart Koopman You are mentioning Media Manager in your tags, is this a custom ECL provider or the Media Manager ECL provider you are using?
Jun 22, 2017 at 19:59 history edited Andy Ross CC BY-SA 3.0
added 6 characters in body
Jun 22, 2017 at 18:01 history asked Andy Ross CC BY-SA 3.0