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

Out of memory on github action #61

Open
waynebrantley opened this issue Feb 6, 2023 · 0 comments
Open

Out of memory on github action #61

waynebrantley opened this issue Feb 6, 2023 · 0 comments

Comments

@waynebrantley
Copy link

Using vite 4.x (any of them) and using this plug-in runs out of memory when running on standard github action linux machine.
I removed the use of the plug-in and just run 'eslint' prior to the vite build (same thing really).
Not sure if this is a vite thing or related to your plug in as far as memory goes. Maybe this plug-in could use memory better or?

2023-02-06T15:01:05.5518796Z [log] �[32m✓�[39m 2314 modules transformed.
2023-02-06T15:01:14.4165828Z [log] rendering chunks...
2023-02-06T15:01:30.3674674Z 
2023-02-06T15:01:30.3675710Z <--- Last few GCs --->
2023-02-06T15:01:30.3676036Z 
2023-02-06T15:01:30.3677362Z [1989:0x6148770]    97286 ms: Scavenge 1995.0 (2065.5) -> 1994.2 (2075.8) MB, 28.2 / 0.0 ms  (average mu = 0.469, current mu = 0.500) allocation failure; 
2023-02-06T15:01:30.3678439Z [1989:0x6148770]    97333 ms: Scavenge 2001.3 (2076.0) -> 1999.0 (2077.2) MB, 11.9 / 0.0 ms  (average mu = 0.469, current mu = 0.500) allocation failure; 
2023-02-06T15:01:30.3679482Z [1989:0x6148770]    98123 ms: Scavenge 2002.5 (2077.4) -> 2000.9 (2096.1) MB, 767.3 / 0.0 ms  (average mu = 0.469, current mu = 0.500) allocation failure; 
2023-02-06T15:01:30.3679860Z 
2023-02-06T15:01:30.3679946Z 
2023-02-06T15:01:30.3680218Z <--- JS stacktrace --->
2023-02-06T15:01:30.3680483Z 
2023-02-06T15:01:30.3681108Z FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
2023-02-06T15:01:30.3681678Z  1: 0xb6b850 node::Abort() [node]
2023-02-06T15:01:30.3686865Z  2: 0xa806a6  [node]
2023-02-06T15:01:30.3692803Z  3: 0xd52140 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
2023-02-06T15:01:30.3698679Z  4: 0xd524e7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
2023-02-06T15:01:30.3705019Z  5: 0xf2fbe5  [node]
2023-02-06T15:01:30.3712032Z  6: 0xf420cd v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
2023-02-06T15:01:30.3718655Z  7: 0xf1c7ce v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
2023-02-06T15:01:30.3725151Z  8: 0xf1db97 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
2023-02-06T15:01:30.3731539Z  9: 0xefed6a v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
2023-02-06T15:01:30.3739371Z 10: 0x12c265f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
2023-02-06T15:01:30.3747505Z 11: 0x16ef479  [node]
2023-02-06T15:02:23.3545229Z Aborted (core dumped)
2023-02-06T15:02:23.3637538Z ##[error]Process completed with exit code 134.
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