Infinite update loop when displaying at least chart twice
When displaying a chart twice there are 2 views (whether visible or not) on the front-end and a single model back-end that is receiving updates from each front-end and sharing the update with all other views. This update replaces the state with a potentially equal but not identical copy which triggers the subscription to again send this information back to the kernel and the cycle repeats.
There is the potential to fix this in the client and make the chart replacement do a smart merge therefore using the same chart (and preventing the equal but not identical update trip) when the chart is equal. The other option is to do a better job in the subscriptions/communication between the front-end and build in this prevention possibly with a deep equals or similar.