Message added on visualize error on forceful termination

README.md

@@ -67,6 +67,8 @@ optimizations on background threads. With worker threads, the CPU will also
 utilize more than 100%. The visible percentage is always the combination of all
 these factors together.
 
+__NOTE__: Exiting the process forcefully can result in wrong or no generation of log files.
+
 ### Windows + PowerShell
 
 In order to diagnose your application with node clinic, you should execute your application after double hyphens(`--`),

bin.js

@@ -413,6 +413,7 @@ async function runTool (toolName, Tool, version, args, uiOptions) {
       if (err) return defer.reject(err)
 
       viz(toolName, filename, function (err) {
+        if (err?.code === 'ENOENT' && err?.message.includes('processstat')) return defer.reject(new Error('Process forcefully closed before processstat file generation'))
         if (err) return defer.reject(err)
         /* istanbul ignore if: isEnabled is always false when spawn process. See: https://github.com/sindresorhus/ora#isenabled */
         if (spinner.isEnabled) {

test/cli-doctor-forceful-termination.test.js

@@ -0,0 +1,17 @@
+'use strict'
+
+const path = require('path')
+const test = require('tap').test
+const cli = require('./cli.js')
+
+test('clinic doctor throws error when process is forcefully closed before processstat file is generated', { skip: process.version.startsWith('v14') }, function (t) {
+  // collect data
+  cli({}, [
+    'clinic', 'doctor', '--no-open',
+    '--', 'node', path.join(__dirname, 'forceful-termination.js')
+  ], function (err, stdout, stderr) {
+    t.ok(err)
+    t.ok(stderr.includes('Process forcefully closed before processstat file generation'))
+    t.end()
+  })
+})

test/forceful-termination.js

@@ -0,0 +1,14 @@
+const async = require('async')
+
+module.exports = function (exit) {
+  async.waterfall([
+    function (next) {
+      next()
+    },
+    function (next) {
+      next()
+    }
+  ], exit)
+}
+
+!module.parent && module.exports(process.exit)