Error code: 5 on Chrome for Mac

marlonjet commented 2 years ago

Verify canary release

[X] I verified that the issue exists in the latest Next.js canary release

Provide environment information

OS: MacOs Catalina OS version: 10.15.7 Browser: Google Chrome Browser version: 104.0.5112.101 Next.js version: 12.1.6

What browser are you using? (if relevant)

Google Chrome

How are you deploying your application? (if relevant)

Plesk

Describe the Bug

Error code: 5 shows when I go through the app I'm building. This error only shows for google chrome for Mac

Expected Behavior

I expect that the website works fine for all browsers

Link to reproduction

https://itd.jetdesigntest.co.uk/

To Reproduce

Click on nav to open the. mega menu

and click these links until the page breaks

SukkaW commented 2 years ago

I am able to reproduce it from the website. However, it is most likely not a Next.js issue.

Here is what you should do:

Grab the crash dump
- Go to chrome://crash, check the checkbox Show developer details
- Grab the UUID from Local Crash Context
Find your Google Chrome crash dump.
- on macOS, it is stored at ~/Library/Application Support/Google/Chrome/Crashpad, under one of three folders.
- Grab the corresponding crash dump from Local Crash Context UUID you get from the last step
Decode the crash dump using the following steps: https://www.chromium.org/developers/decoding-crash-dumps/
You can also submit the issue to the chromium bug tracker to see if anyone could help.

rbutera commented 1 year ago

how did you fix this?

DavidReinberger commented 1 year ago

@marlonjet also interested. Have you ever found a fix?

marlonjet commented 1 year ago

@DavidReinberger @rbutera I had a state to open and close the mega menu. So when I clicked a link (button) it was calling a function that took the user to the page and set the mega menu state to false. I don't know why but I had that issue only on MacOS. The solution I found was to replace those buttons for anchors because they reload the page and turn the mega menu state to false.

cochumo commented 1 year ago

I have the same problem.

chrome version: 110.0.5481.177（Official Build）（arm64）

jamesta696 commented 11 months ago

Version 119.0.6045.199 (Official Build) (arm64) Is there any update or fix for this issue?

My development server is facing the same issue, as soon as I click on the inspector icon to target a specific element in the DOM, the page breaks with this Error Code 5 (Aw Snap!).

I've reinstalled Chrome, cleared Cookies/cache..etc, restarted my Chrome, restarted my laptop and the issues still persists. Any help is appreciated.

Thanks

condorman commented 11 months ago

+1

Edit by maintainers: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

wisefool769 commented 9 months ago

I am experiencing the same thing. I decoded the crash dumps and it says

Operating system: Mac OS X
                  14.2.0 23C64
CPU: arm64
     8 CPUs

GPU: UNKNOWN

Crash reason:  EXC_BREAKPOINT / 0x00000001
Crash address: 0x118743e14
Process uptime: 56 seconds

Thread 0 (crashed)
 0  Google Chrome Framework + 0x4e3e14
     x0 = 0x0000012f016e66e8    x1 = 0x00000000a0000000
     x2 = 0x0000000050000000    x3 = 0x0000000000000000
     x4 = 0x0000000000000000    x5 = 0x0000010c0027fbec
     x6 = 0x000000016fbadc9c    x7 = 0x000000016fbadc48
     x8 = 0x000000007fe00001    x9 = 0x00000000a0000000
    x10 = 0x0000000000000004   x11 = 0x000000000005c000
    x12 = 0x0000000123a18000   x13 = 0x0000010c0430256c
    x14 = 0x00000000ffffffbf   x15 = 0x00000000ffffcf80
    x16 = 0x00000000fff1df80   x17 = 0x000000000073fbb0
    x18 = 0x0000000000000000   x19 = 0x00000000000010bb
    x20 = 0x0000012f016e66e8   x21 = 0x0000010c00dc3c0c
    x22 = 0xaaaaaaaaaaaaaaaa   x23 = 0x0000000000000001
    x24 = 0x0000010c0022f170   x25 = 0x00000000500010bb
    x26 = 0x0000000123a18000   x27 = 0x0000000000000000
    x28 = 0x000000012348f000    fp = 0x000000016fbadec0

What does EXC_BREAKPOINT mean?

CalebMacdonaldBlack commented 9 months ago

I had left this in my globals.css after experimenting some time ago.

@starting-style {
    div {
        background: rgba(0, 0, 0, 0);
    }
}

put that in a fresh nextjs project and it will break

CalebMacdonaldBlack commented 9 months ago

Not nextjs. But something odd with Chrome.

Minimal repro

index.html

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <link rel="stylesheet" href="./style.css">
</head>
<body>
asdf
</body>
</html>

style.css

@starting-style {}

ViggoV commented 1 month ago

This seems to have been caused for me by

@page {
  margin-bottom: 1cm;
  @top-right {
    content: counter(page);
  }
}

Whenever I opened dev-tools. Weird!

vercel / next.js