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
In what situation are you experiencing subpar performance?
We have a customer where insights on a dashboard disappear with the "sad face" icon on the canvas element, after they initially load fine. This is likely due to running out of available memory.
Instrumentation reveals that we have a couple of other people who might be running into the same issue. Since context loss can also appear when devices go into sleep mode etc., we can't know for sure if they are indeed having the issue or if a context can be restored subsequently.
How to reproduce
Unfortunately I can't reproduce this on my end. The relevant dashboards load fine & quickly on my M1 Mac. I wasn't able to build enough memory pressure by opening a lot of tabs with Chrome's memory saver disabled.
Web apps can track events to detect when the page is no longer visible (http://www.w3.org/TR/page-visibility/) and deallocate backing stores at that time by setting the size of the canvas element to 0. Conversely, they can detect when the page is visible again and reinitialize at that time
Web apps can track events that are often associated with GPU context losses (e.g. waking-up from hibernation), and conservatively reinitialize the 2D canvas by resetting the context (set canvas width/height) and redrawing, just in case.
The text was updated successfully, but these errors were encountered:
In what situation are you experiencing subpar performance?
We have a customer where insights on a dashboard disappear with the "sad face" icon on the canvas element, after they initially load fine. This is likely due to running out of available memory.
Instrumentation reveals that we have a couple of other people who might be running into the same issue. Since context loss can also appear when devices go into sleep mode etc., we can't know for sure if they are indeed having the issue or if a context can be restored subsequently.
How to reproduce
Unfortunately I can't reproduce this on my end. The relevant dashboards load fine & quickly on my M1 Mac. I wasn't able to build enough memory pressure by opening a lot of tabs with Chrome's memory saver disabled.
Additional context
There is a known issue with canvas elements, as they can't release memory when unused (like other memory hungry elements do) - see https://wiki.whatwg.org/wiki/Canvas_Context_Loss_and_Restoration. The proposed workarounds could be a potential solution:
The text was updated successfully, but these errors were encountered: