# Severe Chrome lag and unclickable UI when using serverReadyAction in Cursor

**URL:** <https://forum.cursor.com/t/severe-chrome-lag-and-unclickable-ui-when-using-serverreadyaction-in-cursor/74496>\
**Category:** Bug Reports\
**Created:** [April 3, 2025, 3:07am UTC](https://forum.cursor.com/t/severe-chrome-lag-and-unclickable-ui-when-using-serverreadyaction-in-cursor/74496 "2025-04-03T03:07:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jtaki](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jtaki](https://forum.cursor.com/u/jtaki)\
**Post date:** [April 3, 2025, 3:07am UTC](https://forum.cursor.com/t/severe-chrome-lag-and-unclickable-ui-when-using-serverreadyaction-in-cursor/74496/1 "2025-04-03T03:07:31Z")

</div>

**Bug Description:**  
When using `serverReadyAction` to launch Chrome via a debug configuration in Cursor for a `Next.js` app, the resulting Chrome window becomes extremely laggy. The app loads, but UI elements are unclickable or behave inconsistently, and overall page performance drops significantly. Cursor itself also becomes sluggish.

**Steps to Reproduce:**

Use the following `launch.json` configuration:

json

```auto
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Dev Server with Chrome",
      "type": "node-terminal",
      "request": "launch",
      "command": "npm run dev",
      "serverReadyAction": {
        "action": "startDebugging",
        "pattern": "http://localhost:3000",
        "name": "Launch Chrome Browser"
      }
    },
    {
      "name": "Launch Chrome Browser",
      "type": "chrome",
      "request": "launch",
      "url": "http://localhost:3000",
      "webRoot": "${workspaceFolder}"
    }
  ]
}

```

Steps:

1. Run the “Dev Server with Chrome” config.
2. Wait for `http://localhost:3000` to appear in the terminal.
3. Cursor launches Chrome and starts debugging.
4. Observe:

- App becomes extremely slow
- Elements are unclickable or glitchy
- Open the dev console and see that it constantly gets stuck pausing and unpausing the debugger

**Environment Details:**  
Framework: Next.js 13.5.10  
OS: macOS 15.4 (24E248)  
Cursor Version: 0.48.7 (Universal)

**Blocking:**  
Yes — this completely breaks the Chrome + debugger experience in Cursor.  
It works perfectly in VS Code using the exact same `launch.json`.  
Since Chrome launch flags can’t be overridden in Cursor, this can’t be worked around.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [May 3, 2025, 3:08am UTC](https://forum.cursor.com/t/severe-chrome-lag-and-unclickable-ui-when-using-serverreadyaction-in-cursor/74496/2 "2025-05-03T03:08:17Z")

</div>

Closed on May 3, 2025, 3:08am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
