console.timeStamp(...) and performance.mark/measure are missing from the --inspect Performance Timings timeline

Version

20

Platform

No response

Subsystem

No response

What steps will reproduce the bug?

console.profile()

console.timeStamp('Start Rendering')
performance.mark("Start rendering")

function createArr() {
  return new Array(10000).join('x')
}

for (var i=0; i< 1000;i++) {
  createArr()
}

performance.mark("Finish rendering")
performance.measure("Rendering", "Start rendering", "Finish rendering")

console.timeStamp('Finish Rendering')
console.profileEnd()

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

1. Per the node docs on console.timeStamp(...) with the --inspect flag enabled, I should be able to see the timestamp indicated on the performance tab.

2. The User Timings API, performance.mark, and performance.measure show up as "Timings" in the browser's Chrome Dev Tools, but does not show up in node.

What do you see instead?

I don't see any User Timings API calls on the performance timeline.

When using the same performance.* methods in the browser I see them show up in the Performance Timeline.

Additional information

No response

Commencez par reproduire l’exemple avec Node 20 et --inspect, puis comparez la chronologie Performance Timings avec le comportement du navigateur décrit dans l’issue. Suivez la façon dont console.timeStamp, performance.mark et performance.measure sont exposées à l’inspecteur et vérifiez que les horodatages, les marks et les measures apparaissent dans Chrome DevTools.