Google Chrome Memory Usage

Issues
1

What are you trying to do? (please be as specific as possible and include relevant screenshots, code snippets)
My Google chrome memory usage is shooting up to more than 2 GB for the studio and it becomes very difficult to even add an element or do something on the studio. Could you suggest me what to do? Please note it crashes everytime on certain page.

What are the reproduction steps?

Relevant links:

1 Like
2

I run into this issue alot as well and would appreciate some advice.

3

@jason @sarah_ahmed Could you please look into this.

4

Hello @quicksaas, we are investigating memory issues reported on the forum during the past few days, and your issue could be related. Can you please confirm a few things for us:

  • Is it a particular Plasmic component/page within the project where this issue is most noticeable? Can you share the full project URL, including that component/arena id?
  • Are you experiencing these issues in focus mode as well?
5

Issue is with some pages but you can say the more the complex a page gets, more memory it consumes.

I am sharing the most complex page of my project where it happens alot and it is very difficult to work on this page. I mostly work in the focus mode.

https://studio.plasmic.app/projects/u5enwxsNkAs5cmvjfcmPq4/-/Page-Design-3?arena_type=page&arena=sXZq0QYs1-Lk

6

Thank you for the details. We are currently investigating this issue and will keep you posted.

7

Also, I would like to add the issue on the shared page.

Copy and paste of elements doesn’t work in the left side bar.

8

@yang Requesting your attention here. Google chrome Memory usage of the studio is turning out to be a big issue. I am sure you must be aware of this issue and working on it but please if we can prioritize this.

It takes me ages to open previews and then it crashes. I have spent a long time building the product and now it is just becoming difficult to even make some changes in a day.

1 Like
9

We’ve finally gotten to the bottom of the Plasmic Studio crashing issues and believe it is a regression in Chrome versions 127-131. In particular, it disproportionally affects websites using a large number of * CSS selectors (e.g. tailwindcss). Chrome 132 should fully roll out on Jan 14 according to Chromium Dash. Sorry for the inconvenience. Please let us know if you are still experiencing this issue on Chrome 132!