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

Small Time Frames #40

Open
bestchai opened this issue May 27, 2020 · 0 comments
Open

Small Time Frames #40

bestchai opened this issue May 27, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@bestchai
Copy link
Member

bestchai commented May 27, 2020

Rendering the graph on smaller timescales (typically <= 100ns on normal browsers and logs as shown) will cause chrome to run out of memory and crash the program.

Capture.PNG

[Issue created by ashayas: 2016-11-03]
[Last updated on bitbucket: 2016-11-04]

[Comment created by ashayas: 2016-11-04]
One issue is that this is ram dependent but I think if we can assume a more modest ram size for the user and determine thresholds and give this error accordingly it would be best. I will figure out a way that works best.

[Comment created by bestchai: 2016-11-04]
Can you detect when this is a problem (e.g., when number of events is above some limit)? in this case you can show an error to the user telling them that they should select a larger granularity value, or a value above 100 (the more precise the better).

@bestchai bestchai added the bug Something isn't working label May 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant