Hello.
We are using the technique outlined in the documentation to attempt to continuously reconnect to the SignalR server.
In situations where the client is disconnected, and retrying, for an extended period of time, the client side JS memory usage climbs steadily.
Attempting to investigate the issue, it looks like it has to do with onStart event handlers being leaked.
I'm not sure where the issue is, but was wondering if you all had any insight.
We are seeing the issue with SignalR 2.2.0 and jquery 1.10.2.
Thanks for looking.


Hello.
We are using the technique outlined in the documentation to attempt to continuously reconnect to the SignalR server.
In situations where the client is disconnected, and retrying, for an extended period of time, the client side JS memory usage climbs steadily.
Attempting to investigate the issue, it looks like it has to do with onStart event handlers being leaked.
I'm not sure where the issue is, but was wondering if you all had any insight.
We are seeing the issue with SignalR 2.2.0 and jquery 1.10.2.
Thanks for looking.