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
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
The text was updated successfully, but these errors were encountered:
Describe your env
Please provide us your environment, so we can easily reproduce the issue.
pip list | grep dash
belowif frontend related, tell us your Browser, Version and OS
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
The text was updated successfully, but these errors were encountered: