-
Notifications
You must be signed in to change notification settings - Fork 70
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
test broken on report/test-report-fatal-error #153
Comments
Looks like a formatting change on the error. |
Looks like there gc log mixed in. <--- Last few GCs --->
[74857:0x108000000] 283 ms: Mark-sweep 22.7 (55.9) -> 22.6 (55.9) MB, 16.9 / 0.0 ms (average mu = 0.040, current mu = 0.001) allocation failure scavenge might not succeed
[74857:0x108000000] 301 ms: Mark-sweep (reduce) 22.6 (55.9) -> 22.6 (24.9) MB, 17.9 / 0.0 ms (average mu = 0.025, current mu = 0.002) last resort GC in old space requested
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
{"header":{"reportVersion":2,"event":"Allocation failed - JavaScript heap out of memory","trigger":"FatalError ... |
Looks like this is a way to fix: const report = lines.find(i => i.startsWith("{")); |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From latest github CI pipeline.
The text was updated successfully, but these errors were encountered: