Next 15.2 development performance regression #76937
Comments
github-actions
bot
added
Performance
|
Yes, That one i am also facing an issue in latest one 15.2.1 |
|
I thought it was us but indeed there seems to be some regression. |
|
Same here, playwright tests became super flaky and some tests are failing, now I understand why :(( |
This comment has been minimized.
This comment has been minimized.
|
@mikehdt Thank you for submitting an issue! Taking a look— |
samcx
changed the title
|
@mikehdt This may be related to error message improvements via Owner Stacks. It looks like this may alleviate → facebook/react#32529. |
|
Can confirm it is related to Owner Stacks in React! |
|
Interesting. Looks like they're adding a debug helper thing that's got a not-insignificant performance penalty. It feels like if that's the case, it'd be better as an opt-in dev helper than anything like capping its execution times 🤔 It's probably worth questioning setting dependencies on bleeding-edge React commit versions, if something like this regression can get into a minor or patch version without being fully tested. |
github-actions
bot
added
the
linear: next
|
I've just upgraded from 15.1.x to 15.2.x due to the recent CVE and I immediately noticed this issue. What makes it particularly egregious is the fact that the CVE fix hasn't been backported to 15.1.x, so I feel I'm effectively forced to develop with 15.1.7 and then update to 15.2.x before pushing. |
Yes I'm in a similar position, would be great to fix this or back port to 15.1.x |
It seems the PR has been merged and next already bump the react version. |
|
just upgraded to 15.3, but playwright test still flaky and takes longer time to complete |
Link to the code that reproduces this issue
https://github.com/mikehdt/nextjs-15-2-perf-issue
To Reproduce
pnpm ipnpm devClick on some of the buttons and observe performance. There's a lag to the action.
nextinpackage.jsonto15.1.7pnpm ipnpm devThe buttons are noticeably more performant.
Current vs. Expected behavior
There should not be a performance regression?
Using the React dev tools profiler, we can see the difference (this is a slice that shows the render time for clicking one of the buttons):
Next.js 15.1.7
Next.js 15.2.1
Provide environment information
Running on Windows 11 / Node 22 but the env shouldn't really be an issue.Which area(s) are affected? (Select all that apply)
React, Performance
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
It took me three days of trying to debug my own code in a personal project before I realised it wasn't me, it was next.js 😅
The text was updated successfully, but these errors were encountered: