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
Latest versions of one or more @emotion packages causes incredible CPU usage and lag.
Previously we couldn't upgrade @emotion/babel-plugin due to this issue: #3192
We're no longer facing that problem, but instead we're seeing the app become virtually unusable and CPU usage saturating a core whenever Emotion has any work to do.
Based on the commit date of our problem commit (where we upgraded the packages) this must have occurred prior to 11.14.0 - I'm guessing in 11.13.5
To reproduce:
Unknown exactly how to reproduce - but the issue is produced by using the versions of Emotion seen below with the - in front of the line. The + lines are the working versions, taken from our yarn.lock
Upgrades should not add meaningful lag to the application.
Without the problem present
You can see serializeStyles takes some small CPU and murmur2 uses hardly any
With the problem present
serializeStyles and murmur2 eat CPU cycles
I tried upgrading all versions to the latest. I made sure I only had one version of each Emotion subpackage as best I could (eg @emotion/hash, @emotion/memoize, etc) and as far as I can tell I only had one of each.
I noticed when I upgrade everything to the latest, I no longer face #3192, but I wonder if perhaps it's been transmuted into this new problem?
Environment information:
react version: 18.2.0
@emotion/react version: 11.14.0
The text was updated successfully, but these errors were encountered:
Would it be possible for me to get access to your code anyhow or sync on a call in the new year? It's extremely hard to diagnose this without being able to test things out myself in the affected codebase.
Current behavior:
Latest versions of one or more @emotion packages causes incredible CPU usage and lag.
Previously we couldn't upgrade
@emotion/babel-plugin
due to this issue: #3192We're no longer facing that problem, but instead we're seeing the app become virtually unusable and CPU usage saturating a core whenever Emotion has any work to do.
Based on the commit date of our problem commit (where we upgraded the packages) this must have occurred prior to
11.14.0
- I'm guessing in11.13.5
To reproduce:
Unknown exactly how to reproduce - but the issue is produced by using the versions of Emotion seen below with the
-
in front of the line. The+
lines are the working versions, taken from ouryarn.lock
Expected behavior:
Upgrades should not add meaningful lag to the application.
Without the problem present
You can see
serializeStyles
takes some small CPU andmurmur2
uses hardly anyWith the problem present
serializeStyles
andmurmur2
eat CPU cyclesI tried upgrading all versions to the latest. I made sure I only had one version of each Emotion subpackage as best I could (eg
@emotion/hash
,@emotion/memoize
, etc) and as far as I can tell I only had one of each.I noticed when I upgrade everything to the latest, I no longer face #3192, but I wonder if perhaps it's been transmuted into this new problem?
Environment information:
react
version: 18.2.0@emotion/react
version: 11.14.0The text was updated successfully, but these errors were encountered: