Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.
I am surprised to see the API hasn’t changed for almost a year.
This issue was resolved by another post. Essentially EWS was conflicting with another component that failed to release a
NetworkStream(due to aSqlException). 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.