Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able parse GC trace generated for v16.13.2 #1

Open
ashokduraikeg opened this issue Oct 10, 2022 · 0 comments
Open

Not able parse GC trace generated for v16.13.2 #1

ashokduraikeg opened this issue Oct 10, 2022 · 0 comments

Comments

@ashokduraikeg
Copy link

The plugin is not working for Node.js v16.13.2
The sample trace:
[9116:00000187E0A40340] 89 ms: Scavenge 4.4 (4.6) -> 3.7 (5.6) MB, 1.1 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation failure
[9116:00000187E0A40340] 140 ms: Scavenge 4.6 (5.9) -> 4.1 (6.4) MB, 0.6 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation failure
[9116:00000187E0A40340] 192 ms: Scavenge 5.1 (6.4) -> 4.4 (6.9) MB, 0.5 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation failure
[9116:00000187E0A40340] 252 ms: Scavenge 5.6 (6.9) -> 5.1 (9.6) MB, 0.9 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation failure
[9116:00000187E0A40340] 314 ms: Scavenge 7.1 (9.8) -> 6.0 (10.1) MB, 0.9 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation failure
[9116:00000187E0A40340] 399 ms: Scavenge 7.7 (10.4) -> 6.7 (10.9) MB, 1.0 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation failure
[9116:00000187E0A40340] 476 ms: Scavenge 8.5 (10.9) -> 7.5 (16.1) MB, 0.9 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation failure
[9116:00000187E0A40340] 550 ms: Mark-sweep 10.0 (16.1) -> 7.4 (17.1) MB, 7.0 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation failure GC in old space requested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant