Getting started with the sample workload JavaScript Heap out of memory

[asifkazi]

I have consistently seen this happen to the workload sample getting started here: https://learn.microsoft.com/en-us/fabric/workload-development-kit/quickstart-sample#set-up-the-sample-project

1. Whats the point of opening the base URL i.e. http://localhost:60006, The base URL opens up automatically. Shouldnt it just open the /manifest URL, the 60006 just loops never shows any response.

2. Within a few minutes the application runs out of heap memory what is the root cause there?

> [email protected] start
> node validation/validateSchema.js && env-cmd -f .env.dev webpack serve --open --config ./tools/webpack.config.js

******************** Build: Environment Variables *******************
process.env.WORKLOAD_NAME: Org.WorkloadSample
process.env.WORKLOAD_BE_URL: https://localhost:5001
process.env.DEV_AAD_CONFIG_AUDIENCE:
process.env.DEV_AAD_CONFIG_APPID:
process.env.DEV_AAD_CONFIG_REDIRECT_URI: http://localhost:60006/close
*********************************************************************
*********************************************************************
****               Server is listening on port 60006             ****
****   You can now override the Fabric manifest with your own.   ****
*********************************************************************
<i> [webpack-dev-server] Project is running at:
<i> [webpack-dev-server] Loopback: http://localhost:60006/
<i> [webpack-dev-server] On Your Network (IPv4): http://10.211.55.3:60006/
<i> [webpack-dev-server] Content not from webpack is served from 'C:\tools\cygwin\home\asifkazi\Projects\Microsoft-Fabric-workload-development-sample\Frontend\public' directory
<i> [webpack-dev-server] 404s will fallback to '/index.html'
<i> [webpack-dev-middleware] wait until bundle finished: /

<--- Last few GCs --->

[5852:000001AC158E0000]    74421 ms: Mark-Compact 2023.3 (2092.2) -> 2010.0 (2087.5) MB, pooled: 4 MB, 8835.16 / 0.00 ms  (average mu = 0.041, current mu = 0.028) allocation failure; scavenge might not succeed
[5852:000001AC158E0000]    75839 ms: Mark-Compact 2018.3 (2092.4) -> 2011.2 (2088.5) MB, pooled: 4 MB, 1380.12 / 0.00 ms  (average mu = 0.042, current mu = 0.044) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 00007FF6C5775D77 node::SetCppgcReference+17575
 2: 00007FF6C577571B node::SetCppgcReference+15947
 3: 00007FF6C56E2FD4 DSA_meth_get_flags+86340
 4: 00007FF6C634D5D1 v8::Isolate::ReportExternalAllocationLimitReached+65
 5: 00007FF6C633A3F6 v8::Function::Experimental_IsNopFunction+2918
 6: 00007FF6C6184610 v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+31584
 7: 00007FF6C617E2BD v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+6157
 8: 00007FF6C6179B55 v8::CpuProfileNode::GetScriptResourceNameStr+190789
 9: 00007FF6C5A0E24D BIO_ssl_shutdown+189

[omgharra]

Hi @asifkazi,
We tried to reproduce your issue and ran on two different machines without any memory-related issues:

Can you please try run on another machine?

[omgharra]

As for #1, we'll look into it, thanks.

[willwainwright]

We also get this sporadically whilst developing:

[omgharra]

I've created a bug on this and assigned to team - will update on findings - thanks.