Figma On Firefox Linux is slow

Ask the community
1

Hi guys, Figma is running fine on firefox but panning and scrolling is very janky. I searched on the web for any similar issues… didnt find any.

I tried the following

  1. Enable and Disable hardware acceleration
  2. Remove browser cache

On chrome its not so janky… but i use firefox normally.

Firefox Version: 133.0b5 (64-bit) Developer Edition

Thanks in advance.

2

Figma is slow. not just in your firefox, I use the app because its marginally faster as it doesn’t have to contend with the browser - as a whole browsers are power hungry.

Also Bardcore? sounds like that would be legit

3

Hey @Arinjii, sorry for the trouble!

Is this happening with all of your files or only with this particular file? What trouble shooting steps have you tried so far?

  • Logging out and back in
  • Clearing your browser cache
4

must be the file… ya’ll should put that on a t-shirt and send it to all the people using slides

MUST BE THE FILE - DEAD

5

Sorry, not sure i understood… could you elaborate?

6

Its with all my files

  1. Yes i did login and logout
  2. Yup cleared my browser cache, history everything.
  3. Tried enabling and disabling the hardware acceleration… no difference

Do note the performance is very bad on firefox… on chrome its atleast not so janky like it is on firefox… but i use firefox normally… chrome was just to test Figma so would like if the issues could be addressed for firefox :slight_smile:

7

Yea, but its not as slow as on the browser… and i am on linux… so there isnt an app for it (ignoring the linux oss one… i tried it… its very scuffed xD)

Yea bardcore is this new design theme i am making :smiley:

8

sorry Arinjii, I was just trolling Figma becuase their answer for everything is “the file” and not their PERFECT application that has ZERO errors.

:grinning: :grinning:

9

Thanks for the context, @Arinjii!

I’ve added this to our existing bug report. We’re currently aware of issues with scrolling on Firefox becoming more burdensome.

At the moment, there is no ETA for when/if any changes will happen. The best workaround for now from the team is using a different browser, like you’ve already mentioned that you’ve done with Chrome.

1 Like