You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 28, 2024. It is now read-only.
Hi there,
Could you please advise how to correct switch two dashboards every X seconds.
My way:
I made simple datasourcePlugin, whitch is switching pages.
`
(function () {
var pageSwitcher = function (settings, updateCallback) {
var self = this;
var init = false;
var updateTimer = null;
var currentSettings = settings;
But the problem is that after few hours running freeboard not rendering any widget any more. And I have empty panels.
I realized that after each freeboard.gotoPage() are created new instances of widgets. I dont know what happens with old instances. Maybe soem memory problem occures., test PC has 4GB ram and only chrome opened with this page.
Thanks,
Kuan.
The text was updated successfully, but these errors were encountered:
Not sure why I didn't get an issue notification for this before, but it does seem to be a memory leak. A lot of stuff looks to be allocated in knockout.js, and may have to do with one of these issues: http://www.knockmeout.net/2014/10/knockout-cleaning-up.html
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
Could you please advise how to correct switch two dashboards every X seconds.
My way:
I made simple datasourcePlugin, whitch is switching pages.
`
(function () {
var pageSwitcher = function (settings, updateCallback) {
var self = this;
var init = false;
var updateTimer = null;
var currentSettings = settings;
}());
`
But the problem is that after few hours running freeboard not rendering any widget any more. And I have empty panels.
I realized that after each freeboard.gotoPage() are created new instances of widgets. I dont know what happens with old instances. Maybe soem memory problem occures., test PC has 4GB ram and only chrome opened with this page.
Thanks,
Kuan.
The text was updated successfully, but these errors were encountered: