-
-
Notifications
You must be signed in to change notification settings - Fork 34.2k
Closed
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.reportIssues and PRs related to process.report.Issues and PRs related to process.report.
Description
Version
22.10.0
Platform
Linux Tofandel 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
What steps will reproduce the bug?
console.time("report");
process.report.getReport();
console.timeEnd("report");
await fetch('https://example.com/');
console.time("report");
process.report.getReport();
console.timeEnd("report");
await fetch('https://example.com/');
await fetch('https://example.com/');
console.time("report");
process.report.getReport();
console.timeEnd("report");
console.time("report");
process.report.getReport();
console.timeEnd("report");How often does it reproduce? Is there a required condition?
Always, I can reproduce on windows and on linux
What is the expected behavior? Why is that the expected behavior?
The report to not take more than a few milliseconds
What do you see instead?
The report takes 20 additional seconds to generate per fetch request that occured before it (up to 2 fetch, after that it keeps taking 40s)
report: 1.926ms
report: 20.129s
report: 41.714s
report: 40.311sAdditional information
This still happens even with node --report-exclude-network
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.reportIssues and PRs related to process.report.Issues and PRs related to process.report.