Skip to content

GitHub Pagesに公開するためのActionがコケていてPagesにStorybookが反映されない #2

Description

@kaminorse

GitHub Pagesに公開するためのActionがコケていてPagesにStorybookが反映されない

なぜかヒープメモリーが制限をこえてしまっている

> @smartupcorp/react-smarpy@0.0.1 build-storybook
> storybook build

storybook v9.1.10

info => Cleaning outputDir: storybook-static
info => Loading presets
info => Building manager..
info => Building preview..
No story files found for the specified pattern: src/**/*.mdx
info Using tsconfig paths for react-docgen

[vite:dts] You are building a library that may not need to generate declaration files.

vite v6.3.6 building for production...

[vite:lib-inject-css] Current is not in library mode or building process, skip code injection.

Attention: Storybook now collects completely anonymous telemetry regarding usage. This information is used to shape Storybook's roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://storybook.js.org/telemetry

transforming...

<--- Last few GCs --->

[2034:0x14312010]    67731 ms: Mark-Compact (reduce) 2043.8 (2083.7) -> 2043.2 (2083.9) MB, 1809.87 / 0.00 ms  (average mu = 0.244, current mu = 0.006) allocation failure; scavenge might not succeed
[2034:0x14312010]    69550 ms: Mark-Compact (reduce) 2044.4 (2084.2) -> 2044.0 (2084.9) MB, 1816.73 / 0.00 ms  (average mu = 0.130, current mu = 0.001) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

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

 1: 0xb76dc5 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0xee6020 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 3: 0xee6307 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0x10f7f55  [node]
 5: 0x110fdd8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 6: 0x10e5ef1 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 7: 0x10e7085 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 8: 0x10c46d6 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
 9: 0x1520216 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
10: 0x7f3ebbed9ef6 
Aborted (core dumped)
Error: Process completed with exit code 134.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions