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

[BUG] memory ~leak when an interval does not finish? #2198

Open
aiqc opened this issue Aug 17, 2022 · 0 comments
Open

[BUG] memory ~leak when an interval does not finish? #2198

aiqc opened this issue Aug 17, 2022 · 0 comments

Comments

@aiqc
Copy link

aiqc commented Aug 17, 2022

Describe your env

Please provide us your environment, so we can easily reproduce the issue.

  • replace the result of pip list | grep dash below
dash                          2.5.1
dash-bootstrap-components     1.1.0
dash-core-components          2.0.0
dash-html-components          2.0.0
dash-iconify                  0.1.2
dash-table                    5.0.0
  • if frontend related, tell us your Browser, Version and OS

    • OS: macOS 11.6.5
    • Browser: chrome (v103) and firefox (v102)

Describe the bug

OOM when a new interval starts before the last interval finished its callbacks.
For example, if my plot has way too many points so it never finished displaying, and the next interval kicks off before it is finished


Expected behavior

I would expect that when an interval does not finish either:
(a) subsequent intervals would be skipped until the original interval finishes
(b) or, the memory/variables of the original interval is released before the new interval starts

Perhaps this could be configurable


Screenshots

Memory seems to spike when an interval cannot complete within the refresh time, and pressure decreases when i kill the dash server process

Screen Shot 2022-08-17 at 4 52 44 PM

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

1 participant