Screen turns black for a second

Forum|Forum|5 years ago
April 22, 2021
17 replies
4802 views

1. Describe the bug/issue you’re running into?
When I switch back to a tab running FigJam, sometimes my screen turns off / turns black for a second or so. It tends to happen when I haven’t viewed the tabs for at least a few minutes.

2. Are you able to consistently reproduce it? If so what are the steps?
No, but it has happened at least once a day so far.

3. Share a screenshot, recording, console log, link to the file, etc.
It seems to happen on every file I open in FigJam.

4. Is the issue only happening in desktop app or a specific browser , or both?
So far I’ve only used FigJam in the browser on my laptop.

5. What OS/version and/or browser/version are you using?
Chrome: Version 89.0.4389.82 (Official Build) (x86_64)
MacOS Catalina, version 10.15.7

FigJam

This topic has been closed for replies.

Heath_Rogers

Product Support

@babraham Thank you for bringing this to our attention. Please let us know if this continues to happen. If you’re able to grab a screen recording when it happens that would be helpful – though if it’s intermittent that may be hard to do. I’ve went ahead and logged this with our team so they can take a look into this. 🕵️‍♀️

Alice_Ching

Figmate

Hi! Thanks for bringing up this issue!

Could you turn off the “Automatic graphics switching” setting in “System Preferences > Energy Saver”? We are investigating a bug in this area and would like to see if this option is part of the problem!

babrahamAuthor

Figmate

Done! I’ll let you know what happens

babrahamAuthor

Figmate

With “Automatic graphics switching” disabled the problem went away. Also switching tabs back to a figma canvas became faster. Before, there was a very short pause when I switched to a figma tab. This occurred almost all the time. This issue went away as well.

Unfortunately my laptop also started running hotter. Because I often use it in my lap, I decided to reenable “Automatic graphics switching”.

Alice_Ching

Figmate

@babraham That makes sense. Thanks for testing it out for us – we are still looking into this issue and see if we can mitigate it from our side.