Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Doctor has found an unknown issue - Node version 8.11.2

See original GitHub issue

Expected Behavior

To receive recommendations by Node Clinic.

Current Behavior

Right now, node clinic show me the next message: “Doctor has found an unknown issue”

Steps to Reproduce (for bugs)

  1. build my app that use the framework next.js
  2. NODE_ENV=production node_modules/.bin/clinic doctor – node server/run.js
  3. Navigate from different urls that proportionate my server
  4. Control + C
  5. Automatically, in my computer appears a node-clinic html page where appears differents graphics and also the message that says ““Doctor has found an unknown issue””

Sample upload


  • Clinic version: Clinic v1.2.1 Doctor v3.4.0
  • Node version: Node v8.11.2 Npm v6.4.0
  • Browser name and version: Chrome Version 66.0.3359.139 (Official Build) (64-bit)
  • Operating system and version: Fedora 28; Linux x86_64

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:17 (8 by maintainers)

github_iconTop GitHub Comments

mcollinacommented, Sep 23, 2018

Can you please upload the generated output from both flame and bubbleprof? That diagram looks interesting.

If you also can upload a cut-down version of the server, that would also be very interesting to check.

dhairya0904commented, Jun 2, 2021

clinic doctor has suddenly stopped working for me, seems to be a similar issue.

SyntaxError: Unexpected token , in JSON at position 1408
    at JSON.parse (<anonymous>)
    at Parser._transform (/opt/homebrew/lib/node_modules/clinic/node_modules/@nearform/trace-events-parser/index.js:41:34)
    at Parser.Transform._write (node:internal/streams/transform:184:23)
    at writeOrBuffer (node:internal/streams/writable:389:12)
    at _write (node:internal/streams/writable:330:10)
    at Parser.Writable.write (node:internal/streams/writable:334:10)
    at ReadStream.ondata (node:internal/streams/readable:751:22)
    at ReadStream.emit (node:events:365:28)
    at (node:internal/streams/readable:525:10)
    at flow (node:internal/streams/readable:1009:34)
Read more comments on GitHub >

github_iconTop Results From Across the Web

Doctor has found an unknown issue - Node version 8.11.2 #60
build my app that use the framework next. · NODE_ENV=production node_modules/. · Navigate from different urls that proportionate my server ...
Read more >
npm does not support Node.js v12.18.3 - Stack Overflow
I found the work-around ! First you need to open your cmd line, and use " npm install -g npm@latest " you'll get...
Read more >
Keeping Node.js Fast: Tools, Techniques, And Tips For ...
A great tool for diagnosing various performance issues is Node Clinic, ... Note: For this hands-on example we'll need Node 8.11.2 or higher....
Read more >
Documentation - Clinic.js
Clinic.js is a suite of tools to help diagnose and pinpoint your Node.js performance issues.
Read more >
Node JS 19.2.0 - Chocolatey Software
Version Downloads Last Updated Status Node JS 19.3.0 5986 Wednesday, December 14, 2022 Waiting for Maintainer Node JS 19.2.0 27754 Wednesday, November 30, 2022 Approved Node...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found