Thanks for the reply and letting my know that you are checking my issue.
In the meanwhile i was able to narrow down the cause of the leak by reproducing it by starting a fresh project with the Syncfusion toolbar -> Essential studio for winforms -> Create New Syncfusion Project.
I cleared the default page and most of the Site.Master (removed everything from the body except for the , scriptmanager and contentplaceholder),
Put in an asp:Timer with Interval=1000 (just to speed up the process),
Put in a UpdatePanel,
In the UpdatePanel put the trigger for the Timer to cause an AsyncPostBack,
In the ContentTemplate of the UpdatePanel put a CircularGauge from the toolbox and changed it to:
ClientIDMode="static" IsResponsive ="true" runat="server" ID="G1" BackgroundColor="transparent" Load="loadGaugeTheme" AnimationSpeed="200">
So no code behind, just 2 gauges, updatepanel and a timer that triggers the update panel.
Every second the memory usage of chrome increases by like 2-3MB. So im pretty sure the leak isnt from my c# code but from either the UpdatePanel, the CircularGauge or a combination of them both.
---UPDATE---
Removing the IsRepsponsive="true" part from the CircularGauge causes the memory to drop back to normal after 4-5refreshes. So the first 4 cycles it still climbs 2-3MB but after the 5th cycle it drops back to where it started. I dont know exactly what the IsResponsive="true" part does but it was copied from the examples. So for the little test project above that fixed it However it didnt fix it totally for the total project but it is a start.