Closed nilanjansiromani closed 7 months ago
So you are saying this worked in next@11
? Could you add an example/reproduction? :pray: How consistent is the error? Could you share more information on how did you encounter this?
Seems to be a duplicate of #31962
@balazsorban44 The error is persistent and consistent having said that, I had a couple of questions,
We were using the babel loader
The procedure we followed to upgrade was
now do we need to install @swc/core seperately, because i saw next install swc
It depends on the babel plugins you were using. The most common ones are ported or being ported already. If you are missing anything, you could add feedback here about what is missing for you: https://github.com/vercel/next.js/discussions/30174
Apart from that, step 2 and 3 should not be necessary, and you don't have to install @swc/core
either.
At this point, I think your problem is not originating from SWC though unless you can verify that using babel does not reproduce the issue.
If you have a persistent/consistent reproduction, that would be super helpful if you could share! :pray:
thanks ... will revert on this in a couple of days
I have the same problem:
In my case the project runs with docker-compose using the image node:16.13-alpine3.14
, if the project is run on my machine (Intel Mac OS with Big Sur) it works fine, but within the container it crashes.
Other infos that could help is that we use next-transpile-modules
and treat/webpack-plugin
in the next.config.js
.
I resolved my issue adding the following to my next.config.js
:
experimental: {
esmExternals: false,
}
Same here sadly. @federico-moretti that fix didnt work for me. I run a simular setup with it being node:16-slim
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0xb00d90 node::Abort() [node]
2: 0xa1823b node::FatalError(char const*, char const*) [node]
3: 0xcedbce v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
4: 0xcedf47 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
5: 0xea6105 [node]
6: 0xea6be6 [node]
7: 0xeb4b1e [node]
8: 0xeb5560 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
9: 0xeb84de v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
10: 0xe7990a v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
11: 0x11f303c v8::internal::Runtime_AllocateInOldGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
12: 0x15e7819 [node]
Aborted (core dumped)
We had that same issue while deploying in docker on RHEL 7.9 Next.JS v12.0.4 NodeJS: v16.13.0
This is part of our original package.json
"scripts": { "analyze": "cross-env ANALYZE=true next build", "dev": "next dev", "build": "set NODE_OPTIONS=--max-old-space-size=8192 && next build ", "start": "next start", },
We tried changing the max-old-space size to 12192 but it didnt help, we raised it some more to 16192 and it started working again. This is what it looks like now
"scripts": { "analyze": "cross-env ANALYZE=true next build", "dev": "next dev", "build": "set NODE_OPTIONS=--max-old-space-size=16192 && next build ", "start": "next start", },
Hello, I'm having this issue right now. And I've tried every possible solution I had came across but nothing works for me up till now, I still keep getting the error.
<--- Last few GCs --->
[5224:0000024358272890] 384386 ms: Mark-sweep (reduce) 1999.2 (2034.5) -> 1998.2 (2034.5) MB, 10434.1 / 0.0 ms (average mu = 0.114, current mu = 0.006) allocation failure scavenge might not succeed [5224:0000024358272890] 395047 ms: Mark-sweep (reduce) 1999.1 (2034.7) -> 1998.5 (2035.0) MB, 8674.0 / 0.0 ms (average mu = 0.149, current mu = 0.186) allocation failure GC in old space requested
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory 1: 00007FF7228AF4CF v8::internal::CodeObjectRegistry::~CodeObjectRegistry+113967 2: 00007FF72283E4A6 SSL_get_quiet_shutdown+67398 3: 00007FF72283F35D node::OnFatalError+301 4: 00007FF72324A7EE v8::Isolate::ReportExternalAllocationLimitReached+94 5: 00007FF7232349FD v8::Isolate::Exit+653 6: 00007FF7230D658C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1468 7: 00007FF7230D3A56 v8::internal::Heap::CollectGarbage+4294 8: 00007FF7230D13A0 v8::internal::Heap::AllocateExternalBackingStore+1904 9: 00007FF7230F4DF6 v8::internal::Factory::NewFillerObject+214 10: 00007FF722E2121A v8::internal::DateCache::Weekday+1658 11: 00007FF7232DCF71 v8::internal::SetupIsolateDelegate::SetupHeap+513649 12: 000002435A508AD4
Please anyone here knows the solution to the above problem, kindly help me out as I had been on this since four days ago
Please anyone here knows the solution to the above problem, kindly help me out as I had been on this since four days ago
@Tosinkoa are you on a VM, local or container?
I'm still learning @killswitch-GUI can you please explain it?
Thanks to @federico-moretti setting esmExternals: false
solves it for me. Even with the default ESM setting in Next12, not all the ESM packages I use compile well. I still had to use the next-transpile-modules
library to support them.
experimental: {
esmExternals: false,
}
Thanks so much @pmbanugo When I couldn't solve the bug I had to use hard reset using git.
I just upgraded to 12.0.8 hoping this was solved but I am still having the FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
error.
Running:
I just upgraded to 12.0.8 hoping this was solved but I am still having the
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
error.Running:
- Next.js 12.0.8
- Node 16.13.0
- MacOS 12.1
the application now compiles if adding the
experimental: {
esmExternals: false,
},
we also use external packages from our monorepo via next-transpile-module
I am also observing same issue with node: 16.13.1 next: 11.1.3-canary.49
<--- Last few GCs --->
[15036:0x7fd756900000] 1746369 ms: Scavenge (reduce) 3951.9 (4091.4) -> 3951.5 (4091.6) MB, 3.0 / 0.0 ms (average mu = 0.252, current mu = 0.272) allocation failure
[15036:0x7fd756900000] 1748893 ms: Mark-sweep (reduce) 4050.9 (4190.5) -> 4017.1 (4164.5) MB, 2083.6 / 0.1 ms (+ 0.0 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 2089 ms) (average mu = 0.388, current mu = 0.
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
1: 0x10fec1815 node::Abort() (.cold.1) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
2: 0x10ebc0aa9 node::Abort() [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
3: 0x10ebc0c1f node::OnFatalError(char const*, char const*) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
4: 0x10ed41877 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
5: 0x10ed41813 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
6: 0x10eee2c65 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
7: 0x10eee15ec v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
8: 0x10eeedde0 v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
9: 0x10eeede61 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
10: 0x10eeb4c00 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawOneByteInternalizedString(int, unsigned int) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
11: 0x10eeb4aa2 v8::internal::FactoryBase<v8::internal::Factory>::NewOneByteInternalizedString(v8::base::Vector<unsigned char const> const&, unsigned int) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
12: 0x10f18a82a v8::internal::Handle<v8::internal::String> v8::internal::StringTable::LookupKey<v8::internal::SequentialStringKey<unsigned char>, v8::internal::Isolate>(v8::internal::Isolate*, v8::internal::SequentialStringKey<unsigned char>*) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
13: 0x10ed76fb4 void v8::internal::AstValueFactory::Internalize<v8::internal::Isolate>(v8::internal::Isolate*) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
14: 0x10f1adce8 v8::internal::Parser::DoParseProgram(v8::internal::Isolate*, v8::internal::ParseInfo*) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
15: 0x10f1ad2de v8::internal::Parser::ParseProgram(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Script>, v8::internal::ParseInfo*, v8::internal::MaybeHandle<v8::internal::ScopeInfo>) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
16: 0x10f1d7555 v8::internal::parsing::ParseProgram(v8::internal::ParseInfo*, v8::internal::Handle<v8::internal::Script>, v8::internal::MaybeHandle<v8::internal::ScopeInfo>, v8::internal::Isolate*, v8::internal::parsing::ReportStatisticsMode) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
17: 0x10ede26ae v8::internal::(anonymous namespace)::CompileToplevel(v8::internal::ParseInfo*, v8::internal::Handle<v8::internal::Script>, v8::internal::MaybeHandle<v8::internal::ScopeInfo>, v8::internal::Isolate*, v8::internal::IsCompiledScope*) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
18: 0x10ede5572 v8::internal::Compiler::GetWrappedFunction(v8::internal::Handle<v8::internal::String>, v8::internal::Handle<v8::internal::FixedArray>, v8::internal::Handle<v8::internal::Context>, v8::internal::ScriptDetails const&, v8::internal::ScriptData*, v8::ScriptCompiler::CompileOptions, v8::ScriptCompiler::NoCacheReason) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
19: 0x10ed4c70a v8::ScriptCompiler::CompileFunctionInContext(v8::Local<v8::Context>, v8::ScriptCompiler::Source*, unsigned long, v8::Local<v8::String>*, unsigned long, v8::Local<v8::Object>*, v8::ScriptCompiler::CompileOptions, v8::ScriptCompiler::NoCacheReason, v8::Local<v8::ScriptOrModule>*) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
20: 0x10ebb2b0e node::contextify::ContextifyContext::CompileFunction(v8::FunctionCallbackInfo<v8::Value> const&) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
21: 0x10edaa239 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
22: 0x10eda9d06 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) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
23: 0x10eda947f v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
24: 0x10f61a399 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit [/Users/vrajole/.nvm/versions/node/v16.13.1/bin/node]
25: 0x117fd6264
error Command failed with signal "SIGABRT".
Hey, so far we've spent over 10 hours trying to reproduce this and we can't find a problem with Next.js as-is. Please provide a reproduction so that we can continue investigating. A reproduction is a complete repository, sharing the heap allocation failed message unfortunately does not provide any useful data to further investigate.
Hey, so far we've spent over 10 hours trying to reproduce this and we can't find a problem with Next.js as-is. Please provide a reproduction so that we can continue investigating. A reproduction is a complete repository, sharing the heap allocation failed message unfortunately does not provide any useful data to further investigate.
have you troubleshot this both with esmExternal
set to false
and true
?
EDIT: I just tried again and got the same error, the application just doesn't compile without adding the
experimental: {
esmExternals: false,
},
I can't provide a repo to reproduce the error, but we use next-transpile-module
and load around 139 internal packages from our monorepo.
I am running locally "next": "12.0.8",
and
➜ ~ node -v
v16.13.0
➜ ~ yarn -v
1.22.17
➜ ~
Would be interesting to gather whether also previous reporter also make sure of next-transpile-modules
@timneutkens Just like with @floroz We had to disable ESM for it to work. We also use next-transpile-modules
because removing it causes the ESM errors for some packages that are native ESM. So our solution, for now, is to continue with the next-transpile-module
and disable ESM experimental. Maybe they both don't play well together
@timneutkens After a bit of time, we did get our build stable again. As the OP said they tried to add memory but they couldn't get it to build. Our fix was to give our Argo K8S pod 4GB in a relatively small project to build and run in dev mode. As dumb as it sounds this may all be due to the large increase of resources required for Next 12 vs 11! I think it really is an OOM issue, as ours was getting oomkilled. Not saying there isn't a memory leak here tho. After the bump we have been stable on NesxtJS 12 with all features enabled.
Edit: for clarity we previously ran our node at between 512-1GB
have you troubleshot this both with esmExternal set to false and true ?
With it enabled there is no memory leak, memory usage does not increase.
It's likely something in next-transpile-modules
but we can't investigate that without a reproduction as it can be any combination of deps with that enabled.
As I've mentioned we'd be happy to investigate this further but it requires a full reproduction. If none is provided we can't spend more time on it at this point.
@timneutkens After a bit of time, we did get our build stable again. As the OP said they tried to add memory but they couldn't get it to build. Our fix was to give our Argo K8S pod 4GB in a relatively small project to build and run in dev mode. As dumb as it sounds this may all be due to the large increase of resources required for Next 12 vs 11! I think it really is an OOM issue, as ours was getting oomkilled. Not saying there isn't a memory leak here tho. After the bump we have been stable on NesxtJS 12 with all features enabled.
Edit: for clarity we previously ran our node at between 512-1GB
Do you use next-transpile-modules
?
it works fine, but within the container it crashes.
We tackled that, the dev team was mounting in the nodejs modules when they used docker-compose or our K8S tilt dev environments. We had to exclude those from all of our docker builds + only mounting source code since NextJS 12 SWC (Is that true @programbo?) compiler in rust is architecture-dependent when built. Either way we never faced that on 11.
make sure you have node_modules/
in your .dockerignore or **node_modules/
in your .tiltignore.
@pmbanugo not at the moment.
@timneutkens I have the same problem after upgrading from v11 to v12. Used memory on Mac goes up to 2.5GB before it bombs. Previously it was consuming < 1GB on v11. Happy to provide a full reproduction to you via private github. I'm using next-transpile-modules
(required for amcharts4
).
Feel free to share the reproduction with Tim or me! :+1:
@balazsorban44 added you and tim as collaborators - please check branch "crash"
@chrishornmem I have also same issue in a project where I use amcharts
v12.
I removed next-transpile-modules
during update to Next.js 11.1.
I've added @balazsorban44 and @timneutkens as collaborators.
@ddzieduch so your problem is still there on v12 after removing next-transpile-modules
?
Following worked for me in next.config.js
const withTM = require("next-transpile-modules")([
"@amcharts/amcharts4",
]);
module.exports = withTM({
experimental: {
esmExternals: false, // required to stop the FATAL heap crash
},
});
Used memory drops to ~1GB from >2.5GB
@balazsorban44 any update
should I go back to the pre-11.1 settings?
For me, when this stopped the project I was working on for more than a week, and all the solution I found was not helping, I have to do a hard revert using git. I believe a mistake somebody don't know about was made by me.
Suddenly I also faced this issue. I tried changing and reinstalling node and downgrading node to v16 and also Next v11.0 but the issue still exists.
I worked into this project for nearly 4-5 hours, lights went off and I was back to this project but server was running for about an hour of inactivity. And this error happened.
But this worked fine in a blank fresh project. I can share repository if I need. This runs with SWC.
Please let me know if this issue resolves.
Running version:
Node 17.5.0 Next 12.1.0 npm 8.4.1 swc 1.2.2
esmExternals
[FAILED]export NODE_OPTIONS=--max_old_space_size=4096
before start helps. [SUCCESS]It's just on new ubuntu ec2 with 1Gb memory + 4Gb swap.
On MAC works fine without any magic.
@nilanjansiromani regarding https://github.com/vercel/next.js/issues/32314#issuecomment-991833909 were you able to create a reproduction for this?
Anyone else, please note that the best you can do to help with this issue is to provide a reproduction repository that has been simplified to be as minimal as possible but the issue still consistently reproduces. Remove everything that is not necessary for the reproduction, so we can exclude as many variables as possible. :+1:
Refer to Tim's comment: https://github.com/vercel/next.js/issues/32314#issuecomment-1025549719
@chrishornmem we looked into your reproduction, and could not see an immediate problem, but we have suspected for a long time now that next-transpile-modules
plays a part in the problem. We will try to look more into that. We also determined that most likely you can get rid of your .babelrc
config which would result in a faster compilation overall.
@ddzieduch we looked into your reproduction as well, and it does not use Next.js 12. Could you upgrade and see how that works out? We don't backport bugfixes (only security-related) so even if there was a bug, the recommended fix would be to upgrade first.
hey @lokhmakov can you elaborate a little, please. what do you mean run export NODE_OPTIONS=--max_old_space_size=4096
"before start helps." ?
I want to make sure I fully understand what you mean. thanks!
We are also having JavaScript heap out of memory
crashes with a similar setup:
next-transpile-modules
emotion
The error is consistent and persistant. All of our team members have their node processes crash at some point.
I am trying hard to create a reproducible example, but I have no luck yet.
But I noticed a curious thing in our actual project: Some of the webpack cache files (*.pack
) tend to be curiously large with about 200MB, they have 100.000+ LOC
with lines having about 10.000 chars
I am not sure if that is an expected behavior but I thought I might report this to add to the intel
Oh and the long lines are related to emotion
_c = Color70608d;
var colorf83e71 = false ? {
name: "1h3hwmz",
styles: "display:inline-block;width:1em;text-indent:-9999em;background:#f83e71"
} : {
name: "fea5ay-colorf83e71",
styles: "display:inline-block;width:1em;text-indent:-9999em;background:#f83e71;label:colorf83e71;",
map: "/*# sourceMappingURL=data:application/json;charset=utf-8;base64,{"version":3,"sources":["/Users/luke/Projects/next-js-heap-out-of-memory-reproducible-example/ui-library/src/generated_dont_touch/File79.tsx"],"names":[],"mappings":"AAOuB","file":"/Users/luke/Projects/next-js-heap-out-of-memory-reproducible-example/ui-library/src/generated_dont_touch/File79.tsx","sourcesContent":["\n    // import styled from \"@emotion/styled\";\n    import { css } from '@emotion/react'\n    import type { VFC, FC } from \"react\";\n\n    const color70608d = css`display: inline-block; width: 1em; text-indent: -9999em; background: #70608d;`;\n          const Color70608d: FC = ({ children }) => <span css={color70608d}>{children}</span>\nconst colorf83e71 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #f83e71;`;\n          const Colorf83e71: FC = ({ children }) => <span css={colorf83e71}>{children}</span>\nconst color781076 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #781076;`;\n          const Color781076: FC = ({ children }) => <span css={color781076}>{children}</span>\nconst colorc43f94 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #c43f94;`;\n          const Colorc43f94: FC = ({ children }) => <span css={colorc43f94}>{children}</span>\nconst color84dbba = css`display: inline-block; width: 1em; text-indent: -9999em; background: #84dbba;`;\n          const Color84dbba: FC = ({ children }) => <span css={color84dbba}>{children}</span>\nconst color914c24 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #914c24;`;\n          const Color914c24: FC = ({ children }) => <span css={color914c24}>{children}</span>\nconst colorb10385 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #b10385;`;\n          const Colorb10385: FC = ({ children }) => <span css={colorb10385}>{children}</span>\nconst colorf2ac1b = css`display: inline-block; width: 1em; text-indent: -9999em; background: #f2ac1b;`;\n          const Colorf2ac1b: FC = ({ children }) => <span css={colorf2ac1b}>{children}</span>\nconst color093ff9 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #093ff9;`;\n          const Color093ff9: FC = ({ children }) => <span css={color093ff9}>{children}</span>\nconst colorf3eb66 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #f3eb66;`;\n          const Colorf3eb66: FC = ({ children }) => <span css={colorf3eb66}>{children}</span>\nconst colorec0fc1 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #ec0fc1;`;\n          const Colorec0fc1: FC = ({ children }) => <span css={colorec0fc1}>{children}</span>\nconst color6698c9 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #6698c9;`;\n          const Color6698c9: FC = ({ children }) => <span css={color6698c9}>{children}</span>\nconst color11c334 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #11c334;`;\n          const Color11c334: FC = ({ children }) => <span css={color11c334}>{children}</span>\nconst color33d0c4 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #33d0c4;`;\n          const Color33d0c4: FC = ({ children }) => <span css={color33d0c4}>{children}</span>\nconst color906d99 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #906d99;`;\n          const Color906d99: FC = ({ children }) => <span css={color906d99}>{children}</span>\nconst color63ef01 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #63ef01;`;\n          const Color63ef01: FC = ({ children }) => <span css={color63ef01}>{children}</span>\nconst color7a2a48 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #7a2a48;`;\n          const Color7a2a48: FC = ({ children }) => <span css={color7a2a48}>{children}</span>\nconst colorb39c39 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #b39c39;`;\n          const Colorb39c39: FC = ({ children }) => <span css={colorb39c39}>{children}</span>\nconst colorf731d4 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #f731d4;`;\n          const Colorf731d4: FC = ({ children }) => <span css={colorf731d4}>{children}</span>\nconst colorde5195 = css`display: inline-block; width: 1em; text-indent: -9999em; background: #de5195;`;\n          const Colorde5195: FC = ({ children }) => <span css={colorde5195}>{children}</span>\n\n      export const File79: VFC = () => (\n        <p>\n          <Color70608d>70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d70608d</Color70608d>          \n<Colorf83e71>f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71f83e71</Colorf83e71>          \n<Color781076>781076781076781076781076781076781076781076781076781076781076781076781076781076781076781076781076781076781076781076781076</Color781076>          \n<Colorc43f94>c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94c43f94</Colorc43f94>          \n<Color84dbba>84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba84dbba</Color84dbba>          \n<Color914c24>914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24914c24</Color914c24>          \n<Colorb10385>b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385b10385</Colorb10385>          \n<Colorf2ac1b>f2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1bf2ac1b</Colorf2ac1b>          \n<Color093ff9>093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9093ff9</Color093ff9>          \n<Colorf3eb66>f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66f3eb66</Colorf3eb66>          \n<Colorec0fc1>ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1ec0fc1</Colorec0fc1>          \n<Color6698c9>6698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c96698c9</Color6698c9>          \n<Color11c334>11c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c33411c334</Color11c334>          \n<Color33d0c4>33d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c433d0c4</Color33d0c4>          \n<Color906d99>906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99906d99</Color906d99>          \n<Color63ef01>63ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef0163ef01</Color63ef01>          \n<Color7a2a48>7a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a487a2a48</Color7a2a48>          \n<Colorb39c39>b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39b39c39</Colorb39c39>          \n<Colorf731d4>f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4f731d4</Colorf731d4>          \n<Colorde5195>de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195de5195</Colorde5195>\n        </p>\n      );\n  "]} */",
toString: _EMOTION_STRINGIFIED_CSS_ERROR__
};
Others are reporting this at the Webpack Dev Server Repo as well
https://github.com/webpack/webpack-dev-server/issues/1433#issuecomment-1064188349
Emotion seems involved as well.
By now, what I have noticed: The memory appears completely stable. I've been taking regular snapshots over the span of an hour, everything stayed stable at about 18MB. Then, in an instance, there's 4GB of memory allocation and a crash.
I had one curious case where this happened the moment I added a debugger;
statement with open dev tools, but that may have been a cooincidence.
Also something else I am curious of: It may have started at our project when I intoduced a webpack child compiler
. When I did research on this issue I found that often times issues were related to Webpack plugins that use child compilers. But I that is also a shot in the dark to some degree.
I have the same issue with 12.1
And setting:
experimental: {
esmExternals: false,
},
Does not change the issue
I'll try to do a reproduction repo
I also use next-transpile-module
For those using next-transpile-module
, you might want to follow #35150.
I have created a repository nextjs-dynamic-amcharts with the example of the smallest reproduction of the problem..
@balazsorban44 @timneutkens take a look.
@ddzieduch can you describe the steps to take how to trigger the heap overflow?
npm i
add "type": "module"
to node_modules/@amcharts/amcharts4/package.json
and node_modules/@amcharts/amcharts4-geodata/package.json
npm run build
@LukasBombach
Fixed once I realized that esmExternals: false
goes under experimental
, not the root config 🤦
My issue is from using an Nx/Yarn v1 monorepo. It happened with both externalDir
and withTM
. It also affected runtime somehow. So relieved I figured it out.
Before (needed --max-old-space-size
):
After:
i was able to get around this issue by turning the esmexternals flag to false
the way i see, this is the only config change needed to get around this issue
do note this goes under experimentals not the root config like mentioned above
marking this as closed for now thanks everyone for your inputs
What version of Next.js are you using?
12.0.7
What version of Node.js are you using?
16.6.2
What browser are you using?
Chrome / safari
What operating system are you using?
Mac os
How are you deploying your application?
other
Describe the Bug
We have a monorepo with nx wherein we are using next for ssr We have been on next 11 and wanted to move to the next 12 with swc On doing so and making the neccessary changes, our app crashes with
We have tried adding more memory but we feel that the issue lies elsewhere
Expected Behavior
Should work
To Reproduce
NEXT-841