"info - Tailwind CSS is watching for changes..." is duplicated in the CLI output #9004

dmitry-lomakin · 2022-08-01T09:20:04Z

dmitry-lomakin
Aug 1, 2022

What version of Tailwind CSS are you using?

v3.0.0

What build tool (or framework if it abstracts the build tool) are you using?

Angular CLI + @angular-builders/custom-webpack:browser

What version of Node.js are you using?

v12.22.12

What browser are you using?

N/A

What operating system are you using?

macOS

Reproduction URL

N/A

Describe your issue

Hello there!

I'm trying to utilize TailwindCSS in my Angular project and noticed that a dev process (the one that's watching for file changes) started to fail with OOM error. When I rename my tailwind.config.js file (to disable TailwindCSS watcher) I get no OOM even if the process continues working for hours.

One suspicious thing that I'm noticing when watching CLI output is these lines:

[watch] - Generating browser application bundles...
[watch]
[watch] info - Tailwind CSS is watching for changes...
info - https://tailwindcss.com/docs/just-in-time-mode#watch-mode-and-one-off-builds
[watch]
[watch] info - Tailwind CSS is watching for changes...
[watch] info - https://tailwindcss.com/docs/just-in-time-mode#watch-mode-and-one-off-builds

Can you please help me understand and come up with a fix for the issue? I really love the TailwindCSS concept but these OOMs are driving me crazy.

Thanks!

adamwathan · 2022-08-01T10:55:22Z

adamwathan
Aug 1, 2022
Maintainer

Hey, a reproduction most definitely is applicable here, can’t help without it.

0 replies

dmitry-lomakin · 2022-08-01T11:15:53Z

dmitry-lomakin
Aug 1, 2022
Author

It's gonna be challenging to provide a minimal application where the problem can be reproduced, but let me try.

So far I have this - a "greeting" from CLI when the OOM error occurs:

[watch] <--- Last few GCs --->
[watch]
[watch] [18458:0x110008000]  7328374 ms: Mark-sweep 4056.6 (4127.7) -> 4044.0 (4130.2) MB, 5229.1 / 0.3 ms  (average mu = 0.111, current mu = 0.019) allocation failure scavenge might not succeed
[watch] [18458:0x110008000]  7333451 ms: Mark-sweep 4057.6 (4130.2) -> 4045.9 (4132.4) MB, 4995.7 / 2.3 ms  (average mu = 0.065, current mu = 0.016) allocation failure scavenge might not succeed
[watch]
[watch]
[watch] <--- JS stacktrace --->
[watch]
[watch] ==== JS stack trace =========================================
[watch]
[watch]     0: ExitFrame [pc: 0x100a050d9]
[watch] Security context: 0x24110a7008d1 <JSObject>
[watch]     1: exec [0x24110a709a51](this=0x241161802061 <JSRegExp <String[#29]: ^([+-]?\d*\.?\d+)(%|[a-z_]+)?>>,0x241161801fa9 <String[511]\: 5px -5px @nui-shadow-color;\n@nui-shadow-top: 0 -6px 5px -5px var(--nui-shadow-color, @nui-shadow-color);\n\n@nui-shadow-bottom: 0 6px 5px -5px @nui-shadow-color;\n@nui-shadow-bottom: 0 6px 5px -5px var(--nui-shadow-color, @nui-...
[watch]
[watch] FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
[watch]  1: 0x1011f9df5 node::Abort() (.cold.1) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch]  2: 0x1000a66a9 node::Abort() [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch]  3: 0x1000a680f node::OnFatalError(char const*, char const*) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch]  4: 0x1001f0b77 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch]  5: 0x1001f0b17 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch]  6: 0x100387485 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch]  7: 0x100388cda v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch]  8: 0x10038575e v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch]  9: 0x100383510 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch] 10: 0x10038f33a v8::internal::Heap::AllocateRawWithLightRetry(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch] 11: 0x10038f3c1 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch] 12: 0x10035d53a v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch] 13: 0x1006acd88 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]
[watch] 14: 0x100a050d9 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/Users/dmitry.lomakin/.nvm/versions/node/v12.22.12/bin/node]

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

"info - Tailwind CSS is watching for changes..." is duplicated in the CLI output #9004

{{title}}

Replies: 2 comments

{{title}}

{{title}}

Select a reply

"info - Tailwind CSS is watching for changes..." is duplicated in the CLI output #9004

dmitry-lomakin Aug 1, 2022

Replies: 2 comments

adamwathan Aug 1, 2022 Maintainer

dmitry-lomakin Aug 1, 2022 Author

dmitry-lomakin
Aug 1, 2022

adamwathan
Aug 1, 2022
Maintainer

dmitry-lomakin
Aug 1, 2022
Author