<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: deejay96</title>
    <description>The latest articles on DEV Community by deejay96 (@deejay96).</description>
    <link>https://dev.to/deejay96</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F302493%2F4c976d81-9e15-4cee-9845-575fd85db851.png</url>
      <title>DEV Community: deejay96</title>
      <link>https://dev.to/deejay96</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/deejay96"/>
    <language>en</language>
    <item>
      <title>Showing Error in NPM Start</title>
      <dc:creator>deejay96</dc:creator>
      <pubDate>Sat, 28 Dec 2019 05:58:08 +0000</pubDate>
      <link>https://dev.to/deejay96/showing-error-in-npm-start-55na</link>
      <guid>https://dev.to/deejay96/showing-error-in-npm-start-55na</guid>
      <description>&lt;p&gt;Starting the development server...&lt;/p&gt;

&lt;p&gt;&amp;lt;--- Last few GCs ---&amp;gt;&lt;/p&gt;

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

&lt;p&gt;&amp;lt;--- JS stacktrace ---&amp;gt;&lt;/p&gt;

&lt;p&gt;==== JS stack trace =========================================&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;0: ExitFrame [pc: 00000300F02DC5C1]
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;Security context: 0x02630751e6e9 &lt;br&gt;
    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] &lt;a href="https://dev.tothis=0x0315c1b82291%20&amp;lt;BasicSourceMapConsumer%20map%20=%20000002748C4A4389&amp;gt;,aArgs=0x038652c02249%20&amp;lt;Object%20map%20=%200000030C6F7E06B9"&gt;pc=00000300F0B235FB&lt;/a&gt;...&lt;/p&gt;

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

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

</description>
      <category>showingerrorinnpmstart</category>
    </item>
  </channel>
</rss>
