Project

General

Profile

Bug #26097

Stroybook deployment doesn't work

Added by Amir Fefer 6 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Development tools
Target version:
-
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

how to reproduce:

1. run `npm run deploy-storybook`
2. The building stage is frozen due to memory leaks

I'm getting this error when build-stroybook is running:

<--- Last few GCs --->

[26549:0x448e230]    38875 ms: Scavenge 1394.3 (1420.9) -> 1394.4 (1421.4) MB, 3.4 / 0.0 ms  (average mu = 0.171, current mu = 0.077) allocation failure 
[26549:0x448e230]    38882 ms: Scavenge 1394.7 (1421.4) -> 1394.7 (1422.4) MB, 5.0 / 0.0 ms  (average mu = 0.171, current mu = 0.077) allocation failure 
[26549:0x448e230]    40446 ms: Mark-sweep 1395.3 (1422.4) -> 1394.9 (1421.9) MB, 1558.3 / 0.0 ms  (average mu = 0.085, current mu = 0.017) allocation failure scavenge might not succeed

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x372c2c35be1d]
    1: StubFrame [pc: 0x372c2c393d34]
Security context: 0x2f45cb69e6e1 <JSObject>
    2: token(aka token) [0x37be2f49581] [0x24de739026f1 <undefined>:1940] [bytecode=0x39ce14e1ef61 offset=208](this=0x24de739026f1 <undefined>,type=0x24de73906bd1 <String[4]: name>,value=0x3bbc0c938fe9 <String[10]: regExpList>,is_comment=0x24de739026f1 <undefined>)
    3: arguments adaptor frame: 2->3
    4: read_word(ak...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x8dc1c0 node::Abort() [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
 2: 0x8dc20c  [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
 3: 0xad60ae v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
 4: 0xad62e4 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
 5: 0xec3972  [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
 6: 0xec3a78 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
 7: 0xecfb52 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
 8: 0xed0484 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
 9: 0xed30f1 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
10: 0xe9c574 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
11: 0x113beae v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/home/afeferku/.nvm/versions/node/v10.15.1/bin/node]
12: 0x372c2c35be1d 

Associated revisions

Revision 81061b71 (diff)
Added by Ewoud Kohl van Wijngaarden 5 months ago

Refs #26097 - Ignore cross-env in NPM requirements (#3595)

This is only used for storybook building which we don't do in our
packaged builds.

Revision 7e9de250 (diff)
Added by Amir Fefer 5 months ago

Fixes #26097 - fix storybook build and deployment

History

#1 Updated by The Foreman Bot 5 months ago

  • Assignee set to Amir Fefer
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6635 added

#2 Updated by The Foreman Bot 5 months ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/3595 added

#3 Updated by Tomer Brisker 5 months ago

  • Category changed from JavaScript stack to Development tools
  • Fixed in Releases 1.22.0 added

#4 Updated by Amir Fefer 5 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF