Unexpected error during building next.js project - node.js

When I try to build my next.js project I am getting this error:
> next build
info - Creating an optimized production build...
info - Compiled successfully
info - Collecting page data...
info - Generating static pages (0/5)
info - Generating static pages (1/5)
info - Generating static pages (2/5)
info - Generating static pages (3/5)
info - Generating static pages (5/5)
info - Finalizing page optimization...
FATAL ERROR: v8::HandleScope::CreateHandle() Cannot create a handle without a HandleScope
1: 0xa89e60 node::Abort() [node]
2: 0x9ade29 node::FatalError(char const*, char const*) [node]
3: 0xc7555a v8::Utils::ReportApiFailure(char const*, char const*) [node]
4: 0xdfdde2 v8::internal::HandleScope::Extend(v8::internal::Isolate*) [node]
5: 0xe10b7c v8::internal::FactoryBase<v8::internal::Factory>::NewRawOneByteString(int, v8::internal::AllocationType) [node]
6: 0xe22b8e v8::internal::Factory::NewStringFromOneByte(v8::internal::Vector<unsigned char const> const&, v8::internal::AllocationType) [node]
7: 0xc8cf72 v8::String::NewFromOneByte(v8::Isolate*, unsigned char const*, v8::NewStringType, int) [node]
8: 0xc3a317 node::crypto::TLSWrap::InvokeQueued(int, char const*) [node]
9: 0xc3a422 [node]
10: 0xc3a5e4 node::crypto::TLSWrap::~TLSWrap() [node]
11: 0xc3a751 node::crypto::TLSWrap::~TLSWrap() [node]
12: 0xa20c5b node::Environment::RunCleanup() [node]
13: 0x9d670c node::FreeEnvironment(node::Environment*) [node]
14: 0xb52249 node::worker::Worker::Run() [node]
15: 0xb529c8 [node]
16: 0x7ff424e31609 [/lib/x86_64-linux-gnu/libpthread.so.0]
17: 0x7ff424d58293 clone [/lib/x86_64-linux-gnu/libc.so.6]
Aborted
-----> Build failed
Node version: 15.14.0
Npm version: 7.7.6
I do not know why this is failing. It works randomly on local machine an always fails on Heroku. I can't find any solution or related problem.

Related

I am doing an api call and the client is returning a response so big that node crashes

This is the error I am dealing with
#
# Fatal error in , line 0
# Check failed: i::kMaxInt >= len.
#
#
#
#FailureMessage Object: 0x7ffd4a155b80
1: 0xb6d391 [node]
2: 0x1bf6a04 V8_Fatal(char const*, ...) [node]
3: 0xcfcd77 v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [node]
4: 0xbeb719 [node]
5: 0xadb345 [node]
6: 0xd4a82e [node]
7: 0xd4bc4f v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]
8: 0x15e7dd9 [node]
Any assitance here would be greatly appreciated.
Ive tried paging size which does fix this problem because this is on an individual record

random crash in our node app with fatal error

my node program is crashing with the following error. Tried on both node v14.18.1 and v16.13.0.
#
# Fatal error in , line 0
# Check failed: i::kMaxInt >= len.
#
#
#
#FailureMessage Object: 0x7ffd97a48d20
1: 0xaa6321 [node]
2: 0x1a3b274 V8_Fatal(char const*, ...) [node]
3: 0xbcec79 v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [node]
4: 0xb1c319 [node]
5: 0xa14671 [node]
6: 0xc238db [node]
7: 0xc24e86 [node]
8: 0xc25506 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]
9: 0x1446459 [node]
Since there's v8::String::NewFromUtf8 on the stack, and Check failed: i::kMaxInt >= len in the error message, it's pretty clear that your string is too long. On 64-bit platforms, the max string length that V8 supports is ~536 million characters.

Why do I keep getting an Out-Of-Memory error with Redux-Persist?

Occasionally when rebooting my app, my emulator throws this error
Accompanied by this stacktrace
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: node::Abort() [/usr/local/bin/node]
2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node]
3: v8::Utils::ReportOOMFailure(char const*, bool) [/usr/local/bin/node]
4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
5: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
6: v8::internal::String::SlowFlatten(v8::internal::Handle<v8::internal::ConsString>, v8::internal::PretenureFlag) [/usr/local/bin/node]
7: v8::String::WriteUtf8(char*, int, int*, int) const [/usr/local/bin/node]
8: node::StringBytes::Write(v8::Isolate*, char*, unsigned long, v8::Local<v8::Value>, node::encoding, int*) [/usr/local/bin/node]
9: int node::StreamBase::WriteString<(node::encoding)1>(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
10: void node::StreamBase::JSMethod<node::LibuvStreamWrap, &(int node::StreamBase::WriteString<(node::encoding)1>(v8::FunctionCallbackInfo<v8::Value> const&))>(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
11: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) [/usr/local/bin/node]
12: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node]
13: v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node]
14: 0x2672e7c842fd
events.js:183
throw er; // Unhandled 'error' event
^
Error: write EPIPE
at WriteWrap.afterWrite [as oncomplete] (net.js:868:14)
/Users/jisata0/Dev/exampleapp/node_modules/react-native/scripts/packager.sh: line 11: 86698 Abort trap: 6 node "./local-cli/cli.js" start "$#"
Process terminated. Press <enter> to close the window
Can anyone provide some clarity on why this might be happening?
A client is required to review the basic application response to performance improvements. One of the most common causes of performance problems is memory leak.
Out of memory is an error that occurs when the limit of available memory is exceeded.
The simplest way to apply it is to have more memory available to the app.
You can use Add to android / app / src / main / AndroidManifest.xml.
<application android:largeHeap="true"
If you still have out of memory, try debugging any code you've written that uses more memory than you intended or creates a memory lock.

Node js memory heap out on file upload

I am trying to upload a file sized 200MB using angular5 node js. Every time the app crashed with following error.
==== JS stack trace =========================================
Security context: 0x2c3a92b25ee1 <JSObject>
2: SimpleSlice(aka SimpleSlice) [native array.js:1] [bytecode=0x2c3aa14ed689 offset=41](this=0x2c3ad9b02311 <undefined>,p=0x2c3a51d2e961 <Uint8Array map = 0x2c3ad7ec1d91>,O=0,P=217330529,Q=217330529,R=0x2c3a51d6bce1 <JSArray[217330529]>)
4: ArraySliceFallback [native array.js:1] [bytecode=0x2c3aa14ed021 offset=281](this=0x2c3a51d2e961 <Uint8Array map = 0x2c3ad7ec1d91>,at=0,au=0x2c3ad9b02...
FATAL ERROR: invalid table size Allocation failed - JavaScript heap out of memory
1: node::Abort() [/usr/local/bin/node]
2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node]
3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
4: v8::internal::HashTable<v8::internal::SeededNumberDictionary, v8::internal::SeededNumberDictionaryShape>::EnsureCapacity(v8::internal::Handle<v8::internal::SeededNumberDictionary>, int, v8::internal::PretenureFlag) [/usr/local/bin/node]
5: v8::internal::Dictionary<v8::internal::SeededNumberDictionary, v8::internal::SeededNumberDictionaryShape>::Add(v8::internal::Handle<v8::internal::SeededNumberDictionary>, unsigned int, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyDetails, int*) [/usr/local/bin/node]
6: v8::internal::(anonymous namespace)::DictionaryElementsAccessor::AddImpl(v8::internal::Handle<v8::internal::JSObject>, unsigned int, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, unsigned int) [/usr/local/bin/node]
7: v8::internal::JSObject::AddDataElement(v8::internal::Handle<v8::internal::JSObject>, unsigned int, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, v8::internal::Object::ShouldThrow) [/usr/local/bin/node]
8: v8::internal::JSObject::DefineOwnPropertyIgnoreAttributes(v8::internal::LookupIterator*, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, v8::internal::Object::ShouldThrow, v8::internal::JSObject::AccessorInfoHandling) [/usr/local/bin/node]
9: v8::internal::JSObject::CreateDataProperty(v8::internal::LookupIterator*, v8::internal::Handle<v8::internal::Object>, v8::internal::Object::ShouldThrow) [/usr/local/bin/node]
10: v8::internal::Runtime_CreateDataProperty(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
11: 0x12f2c16c6838
I have tried different techniques but all in vein.
--max-old-space-size=80896 --trace-gc-verbose
app.use(bodyParser.json({limit: '8096mb'}));
In activity monitoring when node grab more than 1GB the crash happen.
My development environment is mac with 8 GB ram.

Node.Js (Sails.js) App Crashing Right After Launch - Process Out of Memory: How do I debug?

I've been developing an app with Sails.js (an framework for Node.js) and it's been mostly working well on both my local environment and on AWS. Recently, though, one of the servers has crashed with a "Process Out of Memory" error. In fact, the one server now crashes within a second of running npm start. I've temporarily fixed this issue before by making an image of the server and launching it as a new instance on a larger server, but an immediate crash like this isn't just a matter of needing extra space.
I assume my code has caused a memory leak, but I'm having trouble finding any clues to identify the source of the problem. What are the best tools to debug memory allocation issues in Node.js apps?
Edit: I'm aware of the -inspect flag and I'm poking around with that, but I'm specifically curious of how I might monitor the memory of my app as it runs on a remote server.
Here's the error output from the crashed server, if that's any help. It was running on a t2.large EC2 instance with Node v8.1.2 and npm v5.6.0.
[34mdebug: [39mhookPath: /home/bitnami/emotics-sails-api/node_modules/sails-auth/dist/api/hooks/auth
[34mdebug: [39mmarlinspike (auth): loading config from /home/bitnami/emotics-sails-api/node_modules/sails-auth/dist/config
[34mdebug: [39mmarlinspike (auth): loading Services from /home/bitnami/emotics-sails-api/node_modules/sails-auth/dist/api/services...
[34mdebug: [39mmarlinspike (auth): loading Models...
[34mdebug: [39mmarlinspike (auth): loading Controllers...
[34mdebug: [39mmarlinspike (auth): loading Policies...
[34mdebug: [39m-------------------------------------------------------
[34mdebug: [39m:: Wed Feb 28 2018 05:18:29 GMT+0000 (UTC)
[34mdebug: [39mEnvironment : development
[34mdebug: [39mPort : 80
[34mdebug: [39m-------------------------------------------------------
[31merror: [39mGrunt :: FATAL ERROR: NewSpace::Rebalance Allocation failed - process out of memory
1: node::Abort() [grunt]
2: 0x13647ec [grunt]
3: v8::Utils::ReportOOMFailure(char const*, bool) [grunt]
4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [grunt]
5: 0xa9686b [grunt]
6: v8::internal::MarkCompactCollector::EvacuateNewSpaceAndCandidates() [grunt]
7: v8::internal::MarkCompactCollector::CollectGarbage() [grunt]
8: v8::internal::Heap::MarkCompact() [grunt]
9: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [grunt]
10: v8::internal::Heap::CollectGarbage(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*, v8::GCCallbackFlags) [grunt]
11: v8::internal::Factory::NewWeakCell(v8::internal::Handle<v8::internal::HeapObject>) [grunt]
12: v8::internal::SharedFunctionInfo::SetScript(v8::internal::Handle<v8::internal::SharedFunctionInfo>, v8::internal::Handle<v8::internal::Object>) [grunt]
13: v8::internal::Factory::NewSharedFunctionInfoForLiteral(v8::internal::FunctionLiteral*, v8::internal::Handle<v8::internal::Script>) [grunt]
14: v8::internal::Compiler::GetSharedFunctionInfo(v8::internal::FunctionLiteral*, v8::internal::Handle<v8::internal::Script>, v8::internal::CompilationInfo*) [grunt]
15: v8::internal::FullCodeGenerator::VisitFunctionLiteral(v8::internal::FunctionLiteral*) [grunt]
16: v8::internal::FullCodeGenerator::VisitForAccumulatorValue(v8::internal::Expression*) [grunt]
17: v8::internal::FullCodeGenerator::VisitAssignment(v8::internal::Assignment*) [grunt]
18: v8::internal::FullCodeGenerator::VisitExpressionStatement(v8::internal::ExpressionStatement*) [grunt]
19: v8::internal::FullCodeGenerator::Generate() [grunt]
20: v8::internal::FullCodeGenerator::MakeCode(v8::internal::CompilationInfo*, unsigned long) [grunt]
21: v8::internal::FullCodegenCompilationJob::ExecuteJobImpl() [grunt]
22: v8::internal::CompilationJob::ExecuteJob() [grunt]
23: 0xd97d90 [grunt]
24: 0xd98b28 [grunt]
25: 0xd98d8f [grunt]
26: 0xd9ce59 [grunt]
27: v8::internal::Compiler::Compile(v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Compiler::ClearExceptionFlag) [grunt]
28: v8::internal::Runtime_CompileLazy(int, v8::internal::Object**, v8::internal::Isolate*) [grunt]
29: 0xcf123c0437d
I tried updating npm, but that ran out of memory as well. Is there a way to clear up memory in the CLI? Might there be a process running that I'm not aware of?
bitnami#ip-172-31-##-##:~/my-project$ sudo npm i -g npm
Error: could not get uid/gid
FATAL ERROR: Committing semi space failed. Allocation failed - process out of memory
1: node::Abort() [/opt/bitnami/nodejs/bin/.node.bin]
2: 0x13647ec [/opt/bitnami/nodejs/bin/.node.bin]
3: v8::Utils::ReportOOMFailure(char const*, bool) [/opt/bitnami/nodejs/bin/.node.bin]
4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/opt/bitnami/nodejs/bin/.node.bin]
5: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/opt/bitnami/nodejs/bin/.node.bin]
6: v8::internal::Heap::CollectGarbage(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*, v8::GCCallbackFlags) [/opt/bitnami/nodejs/bin/.node.bin]
7: v8::internal::Factory::NewRawOneByteString(int, v8::internal::PretenureFlag) [/opt/bitnami/nodejs/bin/.node.bin]
8: v8::internal::Factory::NewConsString(v8::internal::Handle<v8::internal::String>, v8::internal::Handle<v8::internal::String>) [/opt/bitnami/nodejs/bin/.node.bin]
9: v8::internal::AstValueFactory::Internalize(v8::internal::Isolate*) [/opt/bitnami/nodejs/bin/.node.bin]
10: 0xd99742 [/opt/bitnami/nodejs/bin/.node.bin]
11: v8::internal::Compiler::GetSharedFunctionInfoForScript(v8::internal::Handle<v8::internal::String>, v8::internal::Handle<v8::internal::Object>, int, int, v8::ScriptOriginOptions, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Context>, v8::Extension*, v8::internal::ScriptData**, v8::ScriptCompiler::CompileOptions, v8::internal::NativesFlag) [/opt/bitnami/nodejs/bin/.node.bin]
12: v8::ScriptCompiler::CompileUnboundInternal(v8::Isolate*, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions) [/opt/bitnami/nodejs/bin/.node.bin]
13: v8::ScriptCompiler::CompileUnboundScript(v8::Isolate*, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions) [/opt/bitnami/nodejs/bin/.node.bin]
14: 0x1393897 [/opt/bitnami/nodejs/bin/.node.bin]
15: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) [/opt/bitnami/nodejs/bin/.node.bin]
16: 0xb43b3b [/opt/bitnami/nodejs/bin/.node.bin]
17: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [/opt/bitnami/nodejs/bin/.node.bin]
18: 0x21e4b490437d
at /opt/bitnami/nodejs/lib/node_modules/npm/node_modules/uid-number/uid-number.js:37:16
at ChildProcess.exithandler (child_process.js:277:5)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:897:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5)
TypeError: Cannot read property 'get' of undefined
at errorHandler (/opt/bitnami/nodejs/lib/node_modules/npm/lib/utils/error-handler.js:205:17)
at /opt/bitnami/nodejs/lib/node_modules/npm/bin/npm-cli.js:83:20
at cb (/opt/bitnami/nodejs/lib/node_modules/npm/lib/npm.js:224:22)
at /opt/bitnami/nodejs/lib/node_modules/npm/lib/npm.js:262:24
at /opt/bitnami/nodejs/lib/node_modules/npm/lib/config/core.js:81:7
at Array.forEach (native)
at /opt/bitnami/nodejs/lib/node_modules/npm/lib/config/core.js:80:13
at f (/opt/bitnami/nodejs/lib/node_modules/npm/node_modules/once/once.js:25:25)
at afterExtras (/opt/bitnami/nodejs/lib/node_modules/npm/lib/config/core.js:178:20)
at Conf.<anonymous> (/opt/bitnami/nodejs/lib/node_modules/npm/lib/config/core.js:236:22)
at /opt/bitnami/nodejs/lib/node_modules/npm/node_modules/uid-number/uid-number.js:39:14
at ChildProcess.exithandler (child_process.js:277:5)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:897:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5)
/opt/bitnami/nodejs/lib/node_modules/npm/lib/utils/error-handler.js:205
if (npm.config.get('json')) {
^
TypeError: Cannot read property 'get' of undefined
at process.errorHandler (/opt/bitnami/nodejs/lib/node_modules/npm/lib/utils/error-handler.js:205:17)
at emitOne (events.js:115:13)
at process.emit (events.js:210:7)
at process._fatalException (bootstrap_node.js:329:26)

Resources