Want to start off by saying thank you for providing this library... while troubleshoo

Main Thread Reported Blocked when idle about node-blocked HOT 1 CLOSED

tj commented on July 28, 2024

Main Thread Reported Blocked when idle

from node-blocked.

Comments (1)

bhedge commented on July 28, 2024

When using blocked-at we had to tune the threshold down very low with the following code:

const http = require('http')
const port = 4000

const blockedAt = require('blocked-at');
blockedAt((time, stack) => {
    console.log(`Blocked for ${time}ms, operation started here:`, stack)
},  {threshold:1, trimFalsePositives:true});

const requestHandler = (request, response) => {
  response.end('{"debug":"return from debug"}')
}

const server = http.createServer(requestHandler)

server.listen(port, (err) => {
  if (err) {
    return console.log('error:', err)
  }

  console.log(`http server listening on port: ${port}`)
})

But we saw many false positives with the blocked-at code itself and a few items from the node internals:

Blocked for 2.17335595703125ms, operation started here: [ '    at HTTPParser.emitInitNative (internal/async_hooks.js:131:43)',
  '    at connectionListenerInternal (_http_server.js:336:10)',
  '    at defaultTriggerAsyncIdScope (internal/async_hooks.js:281:19)',
  '    at Server.connectionListener (_http_server.js:313:3)',
  '    at Server.emit (events.js:180:13)',
  '    at TCP.onconnection (net.js:1558:8)' ]

We want to ensure we can accurately detect main thread blocking as we add each of the elements back to our app and wanted to ask your thoughts on the accuracy of these methods to observe main thread blocking.

from node-blocked.

Recommend Projects