DEV Community 👩‍💻👨‍💻

deejay96
deejay96

Posted on

Showing Error in NPM Start

Starting the development server...

<--- Last few GCs --->

[16088:00000269F06CEF90] 113889 ms: Scavenge 1372.0 (1423.7) -> 1371.2 (1424.2) MB, 5.4 / 0.0 ms (average mu = 0.155, current mu = 0.114) allocation failure
[16088:00000269F06CEF90] 113896 ms: Scavenge 1372.0 (1424.2) -> 1371.2 (1424.7) MB, 5.5 / 0.0 ms (average mu = 0.155, current mu = 0.114) allocation failure
[16088:00000269F06CEF90] 113904 ms: Scavenge 1372.2 (1424.7) -> 1371.3 (1425.2) MB, 6.2 / 0.0 ms (average mu = 0.155, current mu = 0.114) allocation failure

<--- JS stacktrace --->

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

0: ExitFrame [pc: 00000300F02DC5C1]

Security context: 0x02630751e6e9
1: SourceMapConsumer_allGeneratedPositionsFor [000002BDB20489A1] [C:\Users\dhana\Documents\TSE\liveproject\vishal-kids-dashboard\node_modules\@babel\core\node_modules\source-map\lib\source-map-consumer.js:~178] pc=00000300F0B235FB...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 00007FF6365ADD8A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4506
2: 00007FF636588886 node::MakeCallback+4534
3: 00007FF636589200 node_module_register+2032
4: 00007FF6368A30DE v8::internal::FatalProcessOutOfMemory+846
5: 00007FF6368A300F v8::internal::FatalProcessOutOfMemory+639
6: 00007FF636A89804 v8::internal::Heap::MaxHeapGrowingFactor+9620
7: 00007FF636A807E6 v8::internal::ScavengeJob::operator=+24550
8: 00007FF636A7EE3C v8::internal::ScavengeJob::operator=+17980
9: 00007FF636A87B87 v8::internal::Heap::MaxHeapGrowingFactor+2327
10: 00007FF636A87C06 v8::internal::Heap::MaxHeapGrowingFactor+2454
11: 00007FF636BB1EA7 v8::internal::Factory::NewFillerObject+55
12: 00007FF636C2F096 v8::internal::operator<<+73494
13: 00000300F02DC5C1
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! paper-dashboard-react@1.1.0 start: react-scripts start
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the paper-dashboard-react@1.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dhana\AppData\Roaming\npm-cache_logs\2019-12-28T05_50_57_866Z-debug.log
The terminal process terminated with exit code: 1

Top comments (0)

Dream Big


Use any Linode offering to create something unique or silly in the DEV x Linode Hackathon 2022 and win the Wacky Wildcard category.

Join the Hackathon <-