-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incredible lag in recent versions #3300
Comments
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. |
ok |
@Andarist thank you for your reply and my apologies for the delay getting back to you. I can't directly share the code but I'd be happy to try to find a workable approach to allow you access via a remote desktop or something of that sort. Currently I've locked us on these versions as a workaround (Unfortunately we're also working around #3192, which makes it very hard to pinpoint exactly which dependency and version introduced the problem): "@emotion/babel-plugin": "11.10.8",
"@emotion/css": "11.13.4",
"@emotion/react": "11.13.3",
"@emotion/styled": "11.13.0", |
Could we schedule a call to take a look at this together? |
Certainly, and I appreciate your time on this @Andarist! I have a few fires to fight following time off from the holidays, but I can email you to set something up next week at the email list on your profile. Does that sound good? Thank you again! |
Some additional findings today. I ran
And the problem seems to occur after these are upgraded. Notes:
|
yeah, that works |
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
![image](https://private-user-images.githubusercontent.com/6835891/397487679-526caa77-af49-44bc-9e95-bc5fa1e6cadf.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNDUxMTEsIm5iZiI6MTczOTE0NDgxMSwicGF0aCI6Ii82ODM1ODkxLzM5NzQ4NzY3OS01MjZjYWE3Ny1hZjQ5LTQ0YmMtOWU5NS1iYzVmYTFlNmNhZGYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDlUMjM0NjUxWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZjZiNmM3YzkxZjRkNjFiMmY5YTBkYTY5MzhkZDA5OTY1NGE3M2ZjYjViZWY3MzIwNTg1OWM0MDZhNjk2OTI3OCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.q2Ce728i_A9w8xYrSQxhpFpZ2RmkNvUHW58EDv9UsP0)
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: