EWS托管API 1.1-拉订阅内存泄漏 [英] EWS Managed API 1.1 - Pull Subscriptions Memory Leak

问题描述

是否有人在

Has anyone else discovered a memory leak issue with Pull Subscriptions (ExchangeService.SubscribeToPullNotifications()) in Exchange Managed Web Services API? When calling PullSubscription.GetEvents() the memory utilization climbs 4K with nearly every polling call. The only way I've been able to keep the memory utilization down is by forcing garbage collection (via GC.Collect()) after every call - an unnecessary path.

我很惊讶地看到API差不多一年都没有变化.

I am surprised to see the API hasn't changed for almost a year.

推荐答案

ANTS内存分析器用于查明原因和问题的时机.没有这个分析工具，我们将永远不会发现问题.

This issue was resolved by another post. Essentially EWS was conflicting with another component that failed to release a NetworkStream (due to a SqlException). ANTS memory profiler was used to pinpoint the cause and timing of the issue. Without this profiling tool we would have never discovered the problem.

这篇关于EWS托管API 1.1-拉订阅内存泄漏的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！