Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visualizing Many Data Sets hangs browser #2734

Open
fgmart-zz opened this issue Nov 2, 2017 · 2 comments
Open

Visualizing Many Data Sets hangs browser #2734

fgmart-zz opened this issue Nov 2, 2017 · 2 comments

Comments

@fgmart-zz
Copy link

http://isenseproject.org/projects/2437 try to view all data sets and the browser will hang

We should figure out what's wrong (i.e., let's not destroy data sets in an attempt to fix; find the underlying problem instead)

@doug-salvati
Copy link
Contributor

This project was gradually getting slower to load due to increasing number of data sets. Now, it appears it completely never loads. From stack overflow:

"Aw Snap" means that the OS killed the Chrome process for this tab. This happens when your OS thinks that Chrome did something wrong (like when it allocates too much memory, memory corruption, outdated shared libraries after a system patch).

We may need to make the data delivery more efficient in some way, as it seems loading all at once overloads the browser

@doug-salvati doug-salvati changed the title trying to vis project 2437 crashes Visualizing Many Data Sets hangs browser Nov 7, 2017
@doug-salvati
Copy link
Contributor

The issue is that this project has one clever fellow that put in an astronomical amount of jumps. This breaks the following code from line 182 of Histogram.coffee:

# Make 'fake' data to ensure proper bar spacing
fakeDat = for i in [@globalmin...@globalmax] by @configs.binSize
[i, 0]

It's an out of memory error because the array becomes massive. My first impression is that this code snippet looks like a wrong approach to the problem and the whole step should be re-evaluated. Calculating bar spacing should be a constant time operation, not dependent on the amount of integers appearing on the X-Axis.

The offending data set could be removed, to reproduce the issue just add a huge number to your local project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants