large datasets break the graph view

[dasantonym]

the problem seems to be related to the large amount of total streams, even though only a small subset is shown (and is quantized to fewer data points)

[denjello]

that sounds ugly. can you check the javascript heap? is this in browser or in nw?

[denjello]

https://github.com/bnoordhuis/node-heapdump

[denjello]

and then there is this nugget o wisdom: "Providers should not hang on to or even have references to scopes. Angular avoids regenerating scopes wherever possible but there are always times when Angular has to create the scopes from scratch. When this happens the provider's reference will be stale and will leak.Providers should not hang on to or even have references to scopes. Angular avoids regenerating scopes wherever possible but there are always times when Angular has to create the scopes from scratch. When this happens the provider's reference will be stale and will leak." https://github.com/michaelwinser/node-webkit-angular

[denjello]

maybe this helps?

http://nexts.github.io/Clusterize.js/

(Although their demo ALWAYS crashes my mobile firefox...)

[dasantonym]

i'll check but the error currently seems to come from a rather trivial problem that is related to how the api endpoints work and also a bug in the loader on the page (loads too many streams that are not shown, stack size exceeded, no frame count reduction on the server... the lot!)

[fjenett]

I think it would be a better strategy to generate those graphs once on the server (svg?) and then just show them on the page instead of trying to generate them there over and over again.

Currently it is so broken that people can not really use the site because it's impossible to get an overview of which channels are there …