Timeline for ECL Connector Memory Leak
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5, 2017 at 15:30 | comment | added | Alvin Reyes | This was related to logic ECL has to "reconstruct" the location of an external item in the tree/navigation view. Starting with an item from the external system, ECL will ask for the path and recursively get parent items until you get to the mount point. The provider gave the same item rather than its parent (thus the infinite loop). For anyone using the MediaBeacon Connector, do reach out to their Support for the latest version. | |
| Jul 5, 2017 at 15:08 | vote | accept | Andy Ross | ||
| Jul 5, 2017 at 8:21 | comment | added | Yuri Bondarchuk | Indeed. In recent case with MediaBeacon provider. It was provider mistake that created infinite loop. | |
| Jun 23, 2017 at 10:03 | history | answered | Lars Møllebjerg | CC BY-SA 3.0 |