Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix Chrome DevTools source search hangs in Next.js 16 on macOS 26 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#86835•Fetched 2026-04-08 02:09:01
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
emadurandalemadurandal
Participants
BewenbenBewenbenemadurandalemadurandal
Timeline (top)
commented ×1issue_type_added ×1

Code Example

- Next.js: 16.0.7
- Chrome: 142.0.7444.176
- OS: macOS 26.1
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/emadurandal/my-minimal-nextjs-issue-reproduction

To Reproduce

  1. npx create-next-app@latest test-app --yes
  2. cd test-app && npm run dev
  3. Access to localhost:3000 or 127.0.0.1:3000
  4. Open Chrome DevTools
  5. Press Cmd+Shift+F to search sources
  6. Search hangs forever

Current vs. Expected behavior

I expected that search hits something but search hangs forever

Provide environment information

- Next.js: 16.0.7
- Chrome: 142.0.7444.176
- OS: macOS 26.1

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

Works in

  • Next.js 15.3.5
  • Firefox DevTools with Next.js 16

My investigation has revealed that searches hang when using loopback addresses such as localhost:3000 or 127.0.0.1:3000. When accessing via IP addresses such as 192.168.0.2:3000, searches do not hang and successfully return results. I encountered this phenomenon on two Macs (both running macOS 26.1).

This happens in not only my own project but also plane next16.0.7 new project

extent analysis

TL;DR

Accessing the Next.js development server using IP addresses instead of loopback addresses may resolve the search hang issue.

Guidance

  • Verify that the issue is specific to loopback addresses (localhost, 127.0.0.1) by testing with an IP address (e.g., 192.168.0.2).
  • Test the application in a different browser, such as Firefox, to see if the issue is browser-specific.
  • Check if the issue persists when using a previous version of Next.js (e.g., 15.3.5) to confirm if it's a regression.
  • Consider using a tool like host or dig to investigate potential DNS resolution issues with loopback addresses.

Example

No code snippet is provided as the issue seems to be related to environment configuration rather than code.

Notes

The issue appears to be specific to macOS 26.1 and Chrome 142.0.7444.176, but further testing is needed to confirm if it's a platform or browser-specific issue.

Recommendation

Apply workaround: Access the Next.js development server using an IP address instead of a loopback address, as it has been reported to resolve the search hang issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#memory management#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Chrome DevTools source search hangs in Next.js 16 on macOS 26 [1 comments, 2 participants]