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

[bug] [Core dump] FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory #619

Open
arttet opened this issue Sep 16, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@arttet
Copy link

arttet commented Sep 16, 2024

What happened?

<--- Last few GCs --->

ms (average mu = 0.665, current mu = 0.645) task; scavenge might not succeed
[66161:0x7fc991900000] 2367783 ms: Mark-Compact 1981.0 (2095.7) -> 1968.2 (2096.4) MB, 792.00 / 0.00 ms (average mu = 0.534, current mu = 0.431) task; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0x103c74c80 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/Users/runner/runners/2.319.1/externals/node20/bin/node]
2: 0x103e2badc v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/Users/runner/runners/2.319.1/externals/node20/bin/node]
3: 0x10401b877 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/runner/runners/2.319.1/externals/node20/bin/node]
4: 0x10401a0d9 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/runner/runners/2.319.1/externals/node20/bin/node]
5: 0x10409377e v8::internal::MinorGCJob::Task::RunInternal() [/Users/runner/runners/2.319.1/externals/node20/bin/node]
6: 0x103ce412e node::PerIsolatePlatformData::RunForegroundTask(std::__1::unique_ptr<v8::Task, std::__1::default_deletev8::Task>) [/Users/runner/runners/2.319.1/externals/node20/bin/node]
7: 0x103ce2b77 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/Users/runner/runners/2.319.1/externals/node20/bin/node]
8: 0x104791cf1 uv__async_io [/Users/runner/runners/2.319.1/externals/node20/bin/node]
9: 0x1047a568c uv__io_poll [/Users/runner/runners/2.319.1/externals/node20/bin/node]
10: 0x1047922f6 uv_run [/Users/runner/runners/2.319.1/externals/node20/bin/node]
11: 0x103b856f3 node::SpinEventLoopInternal(node::Environment*) [/Users/runner/runners/2.319.1/externals/node20/bin/node]
12: 0x103cbc2ea node::NodeMainInstance::Run(node::ExitCode*, node::Environment*) [/Users/runner/runners/2.319.1/externals/node20/bin/node]
13: 0x103cbbfbc node::NodeMainInstance::Run() [/Users/runner/runners/2.319.1/externals/node20/bin/node]
14: 0x103c36792 node::Start(int, char**) [/Users/runner/runners/2.319.1/externals/node20/bin/node]
15: 0x7ff801e08418 start [/usr/lib/dyld]

What did you expect to happen?

It should not happen.

How can we reproduce it?

You can try to pack the 2 GB directory.

Anything else we need to know?

No response

What version of the action are you using?

v4

What are your runner environments?

macos

Are you on GitHub Enterprise Server? If so, what version?

No response

@arttet arttet added the bug Something isn't working label Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant